[CMake] Making variables visible in ccmake
Dorier, Matthieu
mdorier at anl.gov
Fri Sep 28 07:03:18 EDT 2018
Ah then maybe I don't understand correctly what is supposed to be displayed by ccmake.
In general, how can I have in the ccmake screen some variables displayed to configure some paths to some libraries?
Thanks,
Matthieu
________________________________
From: Eric Noulard <eric.noulard at gmail.com>
Sent: Friday, September 28, 2018 11:30:31 AM
To: Dorier, Matthieu
Cc: CMake Mailinglist
Subject: Re: [CMake] Making variables visible in ccmake
Le ven. 28 sept. 2018 à 11:59, Dorier, Matthieu <mdorier at anl.gov<mailto:mdorier at anl.gov>> a écrit :
Hi,
How do I make a variable visible in the ccmake tool?
For example I would like the user to be able to edit BOOST_ROOT when calling ccmake, how can I do that?
Right now all I see when first running ccmake is "EMPTY_CACHE", and when typing "c" to configure (which fails because some variables aren't properly set) then "e" to exit, I see the variables I have defined with "option", and I can toggle those, but I don't see other variables. I have tried the following:
if(NOT DEFINED BOOST_ROOT)
set(BOOST_ROOT "/usr" CACHE PATH "Root of the Boost installation")
endif(NOT DEFINED BOOST_ROOT)
But I still don't see it in the list of variables.
CACHE variables are "Advanced Variables" which are not displayed unless you toggle display advanced var in either ccmake or cmake-gui.
In ccmake you have to hit 't' in order to see advanced variables.
Additionally, is there a way to have set of variables (namely the options, as well as things like BOOST_ROOT, CMAKE_CXX_COMPILER, CMAKE_C_COMPILER) show up when first calling ccmake, instead of EMPTY_CACHE?
I don't know, CMAKE_<lang>_COMPILER is not meant to be set with cmake UI, they ought to be set in a toolchain or outside.
As noted in CMakeForceCompiler module you should not force them, use toolchain or env var before calling cmake* tool.
--
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20180928/142d0288/attachment-0001.html>
More information about the CMake
mailing list