Telling CMake change the cache location but not Makefile

Asked Aug 08 '17 at 10:25

Active Aug 08 '17 at 10:25

Viewed 95 times

According to the previous answer, I can tell CMake to use use phantom-dir to place cache files in it by using

cmake -H. -Bphantom-dir

However, I need three further customization:

The Makefile should be created inside in the current directory not phantom-dir.
The executable output of Makefile should be in the current directory too.
I need that -H. -Bphantom-dir be embedded in CMakeLists.txt hence a typical user will call cmake in the normal way by cmake .

Are these customizations implementable?

asked Aug 08 '17 at 10:25

ar2015

1

No, I wouldn't create such a system. It might break with every new CMake release. You could atchieve the last point by calling CMake yourself with execute_process, but that has so many disadvantages. – usr1234567 Aug 08 '17 at 10:29
@usr1234567: So, are we destined to tolerate a lot of messy files on the current directory? – ar2015 Aug 08 '17 at 10:31
No, always use a build directory and you are set. – usr1234567 Aug 08 '17 at 11:09
@usr1234567, the build directory does not have access to the resource files unless it uses `../` – ar2015 Aug 08 '17 at 11:14
That's a question of its own. – usr1234567 Aug 08 '17 at 11:55

0 Answers0