-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows 7 and Server 2008
in our master / slave environment cmakebuilder launches CMake with the PATH environment variable set to that as defined on the node, not as potentially expanded by the job via EnvInject.
We use EnvInject to expand the Job's PATH so that it includes the build tool (ninja in our case) and this fails with file not found.
Can cmakebuilder be adjusted to support the use of EnvInject /CustomTool paths?
Thanks,
Brett