Given lite builds, perhaps it can't find nvcc? check your cmakecache.txt to see
if it's pointing to the right executable.
if that doesn't do the trick, change the logging level of the msbuild commands
inside make.bat from minimal to diagnostic and see if that sheds more light on
the actual error.
On 4/7/2018 9:22 AM, The Simple Carnival wrote:
> 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
> error MSB6006: "cmd.exe" exited with code 3.
> Line 170 in the Microsoft.CppCommon.targets file is this:
> 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)"
> 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>
> 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?
> Jeff Boller
> Bf-committers mailing list
Bf-committers mailing list