After fixing a FG build problem (bug), and re-launching MSBuild starts from point zero i.e. downloads files, unzips, and eventually overwrites the files I just fixed.
What would be the good way to tell MSBuild not to start from scratch and preserve my fixes?
Consider a concrete case as follows.
I build on Windows 8.1 64 bit with latest Windows SDK.
cmake 3.0.2
Using Superbuild.
cmake -G "Visual Studio 12 2013 Win64" C:\a03_libs\flightgear\build\fgmeta
Build chokes on OSG:
--------------------------------------------------------------
cd C:\a03_libs\flightgear\build\fgmeta
msbuild /fl /fl:LogFile=build_osg.log OSG.vcxproj
...
Error (problem in osgText):
Glyph.cpp(57): error C2039: 'max' : is not a member of 'std'
Fix Glyph.cpp by adding '#include <algorithm>'
Test the fix works:
cd C:\a03_libs\flightgear\build\fgmeta\osgbuild\src\osgText\
msbuild osgText.vcxproj (build is OK)
Now let's try re-building the whole OSG again
-------------------------------------------------------------
cd C:\a03_libs\flightgear\build\fgmeta
msbuild /fl /fl:LogFile=build_osg.log OSG.vcxproj
---
Now MSBuild downloads OSG, unzips and overwrites the fixed 'Glyph.cpp', and then runs for hours before throwing the same error. Cannot even stop it somehow other then killing.
So, what's the best way to proceed?
Appreciate your help and time.