Sparrow does not report failure to open binary file for writing as an error

[Nikos Mouchtaris]

If a target binary code file (result of compiling a source file) cannot be opened for writing (for example, when the path to it does not exist), sparrow does not report this error as an error on its errors window. It also does not consider the build failed.

Example:

1.2>---------------- Build started: Script SolutionData.dsc ----------------
1.2>Started compiling 'SolutionLoader/Source/SolutionData.dsc'.
1.2>Finished compiling 'SolutionLoader/Source/SolutionData.dsc', NO ERRORS detected.
1.2>Finished compiling 'SolutionLoader/Source/SolutionData.dsc', NO WARNINGS reported.
1.2>Failed to open file 'C:/Users/TURBO_X/Documents/uni/UOC/CSD/metaterrestrial/saviwork/vcproj2make/deltaide2make/SolutionLoader/Project/../Lib/SolutionData.dbc' to write target code (No error)Failed to open file 'C:/Users/TURBO_X/Documents/uni/UOC/CSD/metaterrestrial/saviwork/vcproj2make/deltaide2make/SolutionLoader/Project/../Lib/SolutionData.idc' for writing intermediate code (No error).
1.2>---------------- Script SolutionData.dsc: Build completed ----------------