You can use the new OBJECT library feature introduced in CMake 2.8.8. The idea is explained here. Basically, the OBJECT library is a similar concept to the convenience library known from Autotools to group object files. Check the complete CMake OBJECT library tutorial.
There are several approaches for detect and discard inclusion of the project, which has already be included in some other parts of the main project. Check project’s target existence The simplest pattern for single inclusion of subproject is checking existence of some subproject’s target: # When include ‘C’ subproject if(NOT TARGET library_C) add_subdirectory(C) endif() (Here … Read more
Typical CMake scripts like FindGLEW will define variables that specify the paths and files that your project needs. If the script can’t automatically identify the correct paths (usually because of nonstandard install location, which is fine), then it leaves these variables up to you to fill in. With command line CMake, you use the -D … Read more
You can use the undocumented command line options -B and -H to specify your build directory and source directory respectively. So, from your project’s root, you can do: cmake -Bbuild -H. (Where build is your build directory path.)
You ran into a rather annoying “it’s not a bug, it’s a feature” behavior of CMake. As explained in the documentation of the if command: The if command was written very early in CMake’s history, predating the ${} variable evaluation syntax, and for convenience evaluates variables named by its arguments as shown in the above … Read more
The origin of the problem is not the target_include_directories command itself, but the attempt to install a target that has a public or interface include directory prefixed in the source path (i.e. the include directory is a subdirectory of your ${PROJECT_SOURCE_DIR}.) While it is perfectly fine and desirable to use absolute paths when building the … Read more
CMake now supports this with versions 3.6 and higher through the VS_STARTUP_PROJECT directory property: cmake_minimum_required(VERSION 3.6) project(foo) # … add_executable(bar ${BAR_SOURCES}) set_property(DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR} PROPERTY VS_STARTUP_PROJECT bar) This will set bar as the startup project for the foo.sln solution.
Since version 2.8, the file command has a COPY sub-command: file(COPY yourDir DESTINATION yourDestination) Note that: Relative input paths are evaluated with respect to the current source directory, and a relative destination is evaluated with respect to the current build directory
cmake -LAH To list all option(…) and set(… CACHE …) variables, including those marked as advanced, do: cmake -LAH where: -L: list variables -A: include advanced variables. CMake marks most but not all of its default pre-defined variables as, and you can mark you own variables as advanced with mark_as_advanced). Some default CMake advanced variables … Read more
There is no interactive debugger for CMake, however there are also the flags -Wdev, –debug-output and –trace which might help. Also remember to check the log files CMakeFiles\CMakeOutput.log and CMakeFiles\CMakeError.log which mainly collect outputs of processes called by CMake (for example while checking for presence of a type or header). Since version 3.7, CMake now … Read more