#CMAKE INCLUDE ALL BUT INSTALL#
#CMAKE INCLUDE ALL BUT PORTABLE#
#CMAKE INCLUDE ALL BUT WINDOWS#

#CMAKE INCLUDE ALL BUT WINDOWS#

To concatenate the commands, both on Unix and Windows you can use This solves the problem of installing a specific target together with its dependencies!

#CMAKE INCLUDE ALL BUT INSTALL#

This will install all the libraries you have built, those you mentioned explicitly and those to which they depended.

This will build all the targets listed and their dependencies Set to OPTIONAL installation of all targets you do not want to always build: Set(CMAKE_SKIP_INSTALL_ALL_DEPENDENCY true) Remove dependency of 'install' target to 'all' target (once, in the main CMakeLists.txt): What one understands from the cmake documentation is that OPTIONAL should be put as last option. This INSTALL command install(TARGETS $ OPTIONAL RUNTIME DESTINATION. (I am using 2.8.11 under Windows, also tested 2.8.10) In the main CMakeLists.txt file, and I omit all EXCLUDE_FROM_ALL, put installation of as many targets as I want optional (in my case, all but A), and if building of specific targets precede installation, yet the command: ninja -j7 D & ninja installįor some reason will fail, stating that C (whose installation was set to OPTIONAL) does not exist (it was not created because D depended only on A and B)… file INSTALL cannot find ''

I tried putting EXCLUDE_FROM_ALL as an option of add_subdirectory (instead of add_library/add_executable), but then all the install statements in those sub-directory seem to be ignored: only install statements in non excluded-from-all subdirectories will be installed.Įven if I activate CMAKE_SKIP_INSTALL_ALL_DEPENDENCY: set(CMAKE_SKIP_INSTALL_ALL_DEPENDENCY true) CMake does not define behavior for this case. I also get this warning: Target has EXCLUDE_FROM_ALL set and will not be built by default but an install rule has been provided for it. Reading better in the documentation I found out that: Installing a target with EXCLUDE_FROM_ALL set to true has undefined behavior. I tried the strategy I proposed, but it didn't work: in my case, putting an install statement for a target (even if specified as OPTIONAL) will make ineffective EXCLUDE_FROM_ALL.

#CMAKE INCLUDE ALL BUT PORTABLE#

The solution should be portable to different OSs. We would like to avoid that everybody has to edit the main CMakeLists.txt file to exclude projects he is not interested in. Is it going to work? Is there any better solution?

I add one extra subproject that simply depends from all other sub-projects (maybe I make each target publish its name by using some variable set at PARENT_SCOPE), and people will have to call that when they want to build and install everything.

Apart from subproject A, all other targets are set to EXCLUDE_FROM_ALL, and OPTIONAL at installation.

So I am thinking of the following strategy: But going in that direction I couldn't find any solution. So EXCLUDE_FROM_ALL wouldn't be an option. I would like to keep that the target all keep building everything. Instead, it builds the target all and install all. It only built D (and dependencies) and then installed only D and its dependencies (A and B). I would like that if I call: ninja -j7 D install Perfect.īut how can I call install only for D without triggering build all? This will also build A and B if something for them has changed. If I am working on D, I can easily build 'only' D by calling cmake -build. But people would like also to be able to work only on one of these projects, and not having to build/install everything everytime. The main CMakeLists.txt file should include all directories, so that the build all builds everything. Now: many people are working on these projects. Plus, there might be some further dependencies: Let's say I have a project made of several subprojects A, B, C, D…Īll subprojects depends on A, which changes rather frequently.

Cmake include all but