MantisBT - CMake
View Issue Details
0016055CMakeCMakepublic2016-04-07 16:582016-06-10 14:31
Daniel Richard G. 
Kitware Robot 
normalminoralways
closedmoved 
Windows
CMake 3.5.1 
 
0016055: "nmake" program is not found using MAKE environment variable
If you set MAKE=C:\path\to\nmake.exe in your environment, but nmake is not in your PATH, then the NMake generator will fail.

Looking for nmake in the current PATH is reasonable, but if MAKE is defined, then that should be used instead.
No tags attached.
Issue History
2016-04-07 16:58Daniel Richard G.New Issue
2016-04-08 08:30Brad KingNote Added: 0040829
2016-04-08 15:24Daniel Richard G.Note Added: 0040833
2016-06-10 14:29Kitware RobotNote Added: 0042979
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0040829)
Brad King   
2016-04-08 08:30   
One may pre-populate the cache with CMAKE_MAKE_PROGRAM set to the desired program.
(0040833)
Daniel Richard G.   
2016-04-08 15:24   
Right, but if MAKE is set then that should be used. Same way that CMAKE_C_COMPILER uses CC if set, or CMAKE_C_FLAGS uses CFLAGS.

The ideal, of course, is to support the "standard" environment variables where those are applicable. If someone doesn't have a priori knowledge about CMake, it could take them a lot of digging to find out about CMAKE_MAKE_PROGRAM. But they are likely to know about MAKE because other build systems use that.

(I run into this kind of frustration whenever I have to deal with the rare SCons-based project, because every time, I have to re-figure-out the completely non-obvious way necessary to specify my own compiler flags since CFLAGS is completely ignored...)
(0042979)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.