#Important cmake variables full version#

But, non-CACHE'd variables are meant to be transient, so I'm not sure why you would need them outside of a build environment anyway. If your variables are marked as INTERNAL or not CACHE'd at all, then there is no method within CMake to pull it out. And it will not show any that are cached INTERNAL, and will only show ADVANCED if -LA is used instead of -L. The issue though is that it will not show any variables that are not marked with CACHE. So, it does show variables from other files. Build files have been written to: /home/tgallagher/cmaketest-build Check for working CXX compiler: /usr/bin/c++ - works Check for working CXX compiler: /usr/bin/c++ Typical entries include Debug, Release, RelWithDebInfo and MinSizeRel, but custom build types can also be defined. Visual Studio, Xcode, or Ninja Multi-Config) as a semicolon-separated list. Check for working C compiler: /usr/bin/gcc - works Specifies the available build types (configurations) on multi-config generators (e.g. It is only different when a different version of CMake is run on a previously created cache file. Common tasks like linking against a module should be done through the library targets each module defines.

Note: You rarely need to access these variables directly. This stores the major version of CMake used to write a CMake cache file. CMake Variable Reference Module variables Qt modules loaded with findpackage set various variables. Check for working C compiler: /usr/bin/gcc CMAKECACHEMAJORVERSION¶ Major version of CMake used to create the CMakeCache.txt file. Gives: - The C compiler identification is GNU The command (run from another directory): cmake -L. Of course, if you only want the value, you can do: cmake -L /path/to/CMakeLists.txt | grep MY_CMAKE_VARIABLE | cut -d '=' -f2įor example, with a CMakeLists.txt that is: cmake_minimum_required(VERSION 2.8)Īnd where otherFile.txt is: set(MY_OTHER_VAR 'Hi' CACHE STRING '') This variable is defined by versions 2.6.3 and higher.

#Important cmake variables full version#

This specifies the full version of the CMake executable being run. If it is an advanced variable, add the -A flag to the same command and it will include advanced variables. CMAKEVERSION: The full version of cmake in -id format. Which will return to you something like := If you do not yet have a cache file and you want to see what options there are in a CMakeLists.txt file, you can do (in a different directory since this will write a cache file): cmake -L /path/to/CMakeLists.txt | grep MY_CMAKE_VARIABLE Which sets the CMake variable GDCM_DIR to a CMake cache variable if the environment variable GDCM_DIR is set.If you have an existing cache file, you can do: grep MY_CMAKE_VARIABLE CMakeCache.txt For example: set (INCLUDE_DIR $ENV' STREQUAL '')Īn example usage of this CMake function is define_from_environment(GDCM_DIR GDCM) One option is to use an environment variable to set a CMake variable. But it would be nice to just define these variables once and make everything else take them into account. It should work fine, and is probably what I'll do if I can't make it work otherwise.

Is there another, less ugly solution, solution for fixing it for INCLUDE_DIR as well?Ī backup solution is to let the top makefile define CMAKE variables.

How do I make sure that the expansion works for the make variable LIB_DIR passed though cmake to the generated makefile? Since it is make that runs the linker (I think?) I don't see why it wouldn't expand.

Removing the leading slash gives a warning about relative paths, and the link command has still the unexpanded $LIB_DIR. The link command that I see upon building has the literal string -L/$(LIB_DIR). This solution does not work for linking: LINK_DIRECTORIES('/$(LIB_DIR)') Without it, the content of INCLUDE_DIR gets prefixed by the cmake project root (it is then considered a relative path).

The string is passed as is all the way to the generated makefile, and is then expanded by make upon building. My problem is that I cannot pass all these make variables to the projects that use cmake.įor the include directory, this work-around in CMakeLists.txt works: INCLUDE_DIRECTORIES('/$(INCLUDE_DIR)') The makefile at the top defines make variables for pathes to libs, includes, and binaries. The top project has a makefile, which is used to trigger the build of the submodules. Some modules use make only, others use cmake. I have a projects that consists of modules that are built separately.