[Bf-committers] MSBuild problems with ZERO_CHECK project

[The Simple Carnival]

Hello --

I recently reinstalled Windows and am trying to compile Blender 2.78c, 
which I was able to do with my previous Windows installation. I suspect 
there is a CMake issue, but I'm not sure exactly how to address it.

I'm running into problems when trying to create the Blender Release 
version. (I can create the Lite version without problems.) Specifically, 
I'll use the following command...

c:\blender-git\blender>make release

...and then I will quickly receive this error:

The system cannot find the path specified.
C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): 
error MSB6006: "cmd.exe" exited with code 3. 
[C:\blender-git\build_windows_Release_x64_vc12_Release\ZERO_CHECK.vcxproj]

Line 170 in the Microsoft.CppCommon.targets file is this:

     <CustomBuild

       Sources                     ="@(CustomBuild)"
       BuildSuffix                 ="$(_BuildSuffix)"

       TrackerLogDirectory ="%(CustomBuild.TrackerLogDirectory)"
       MinimalRebuildFromTracking 
="%(CustomBuild.MinimalRebuildFromTracking)"

       TLogReadFiles ="@(CustomBuildTLogReadFiles)"
       TLogWriteFiles ="@(CustomBuildTLogWriteFiles)"
       TrackFileAccess             ="$(TrackFileAccess)"
       ToolArchitecture ="$(CustomBuildToolArchitecture)"
       TrackerFrameworkPath ="$(CustomBuildTrackerFrameworkPath)"
       TrackerSdkPath ="$(CustomBuildTrackerSdkPath)"

       AcceptableNonZeroExitCodes 
="%(CustomBuild.AcceptableNonZeroExitCodes)"
       >
     </CustomBuild>


One of those paths is apparently bad, but I'm not sure which...nor have 
I been able to figure out how to print that information from MSBuild.

I temporarily replaced the entire target where that CustomBuild appears 
with some junk code:

   <Target Name="CustomBuild">
       <Message Text="GOT HERE!!!!!!!!!!!!!!!"></Message>
   </Target>

I can't see the message text in the console window, but I was at least 
able to build the Blender release version successfully.

Although this "fix" worked, it's obviously not addressing the root 
problem. Any ideas on what's going on here, and how I can get my Blender 
build files to compile without this workaround?

Thanks!

Jeff Boller
http://www.sundriftproductions.com