I'm just porting a huge solution (MFC, lot's of DLL subprojects) from VS 2008 to VS 2010, everything compiles and links fine normally, but from time to time the build stops with an error caused by BSCMAKE, something like this:
> BSCMAKE: error BK1505 : cannot read from file '.\Debug\Netlist.bsc'
This project 'Netlist' is quite large (about 400 files, the generated SBR files have about 3,5 GB all together allthough the generated BSC file is just about 11 KB which I think is strange too since in most other projects the BSC files are > 10 MB), but as told in general it builds fine but after some time working with it the error occurs.
The only way to resolve the error I found up to now is to delede the mentioned BSC file - then the next build gives an error like this:
> BSCMAKE : warning BK4502: truncated .SBR file '.\Debug\<filexy>.sbr' not in .\debug/Netlist.bsc
> BSCMAKE : error BK1513: nonincremental update requires all .SBR files
varies from time to time.
After this the next build compiles/links fine without any error.
I tried to find the reason and/or a way to workaround that annoying error which forces me to build the project three times with deleting the BSC file in between, but I cannot find any more info about this then:
> BSCMAKE cannot read from the file.
> To fix by checking the following possible causes
> 1. File corruption.
> 2. File truncation to the compiler running out of disk space or being interrupted while creating the .sbr file.
I have enough free disk space, so this cannot be the cause - sometimes I interrupt the build process, but I don't think this is the cause since mostly the error occured even after I built some times without interrupting.
And, I never encountered the same problem with VS 2008 ...
I know I can avoid this problem by either disabling browse info at all (but I don't want to do this) or by passing the option '/n' to BSC make, but this will cause a full rebuild of browse info and this consumes quite a lot of time.
Now I want to ask if anyone of you had similar problems and probabyl found another workaround ...
Thanks in advance,