Why doesn't "CMAKE_MAKE_PROGRAM" variable take effect?

Question

I try to use gmake instead of make as the build command. So I modify the CMakeList.txt as following:

......
set(CMAKE_MAKE_PROGRAM /usr/local/bin/gmake)
......

While in CMakeCache.txt, CMAKE_MAKE_PROGRAM is still /usr/bin/make:

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make

How to make "CMAKE_MAKE_PROGRAM" variable take effect?

@arrowd Unfortunately, it reminds me "set given invalid arguments for CACHE mode.". — Nan Xiao
– Nan Xiao, Commented Mar 5, 2018 at 7:43

thomas_f · Accepted Answer · 2018-03-05 08:00:10Z

3

You have two options:

1: Set the make command when you call CMake: cmake -DCMAKE_MAKE_PROGRAM=gmake <the rest of your arguments>

2: Do as @arrowd hinted in the comments, but use the correct syntax: set(CMAKE_MAKE_PROGRAM gmake CACHE FILEPATH "" FORCE) or set(CMAKE_MAKE_PROGRAM gmake CACHE INTERNAL ""). The latter will hide the setting from cmake-gui.

Both of these assume that gmake is in your PATH, othwerwise you must specify a full path to gmake.

answered Mar 5, 2018 at 8:00

thomas_f

2,04322 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why doesn't "CMAKE_MAKE_PROGRAM" variable take effect?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related