[CMake] CMake Checks Cache

Hi, If you use CMake in a CI you should probably have a look at how to speed up your CMake build: https://github.com/cristianadam/cmake-checks-cache In the case of LLVM + Clang on a Windows box the speed up was either 2.66x or 3.32x, depending on the CMake generator. Even if you don't use CMake

[Cmake-commits] CMake branch, master, updated. v3.11.1-580-g3db4092

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180423) +set(CMake_VERSION_PATCH 20180424) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] UNKNOWN IMPORTED vs INTERFACE IMPORTED for non-CMake library

Hi, I somewhat recently filed a bug report regarding target_link_libraries favoring target names over library names (https://gitlab.kitware.com/cmake/cmake/issues/17911). Brad King suggested also that I switch to UNKNOWN instead of INTERFACE for the IMPORTed targets created by my find-modules.

Re: [CMake] Spaces in var=value list in *_command

Are you trying to construct a BUILD_COMMAND line that looks like CXXFLAGS=-g -02 -w && ./configure? If so, you should be able to do that with the CMake -E env command option like this ( Starting in CMake 3.1 ): set(cxx_flags "-g -O2 -w") set(command_to_run ${CMAKE_COMMAND} -E environment)

Re: [CMake] Generating MSVS solution files that can be passed around

One thing to consider is that MS is now shipping CMake as part of VS.  So, if you can get your project to work with that version of VS, you should be all set. In fact you can have people just open the project and MS VS will run CMake for you. -Bill -- Powered by www.kitware.com Please keep

[Cmake-commits] CMake branch, master, updated. v3.11.1-579-gf9b3b5a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via f9b3b5a7730e1c8b87742bcff516acaed7fa7882 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-575-g97ecefa

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 97ecefa73b54b7c585e2e16cee844b943ccf062f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-562-gc74539a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c74539aad738e7ceddaa223b0edb622724b6a2e2 (commit) via

Re: [CMake] Generator expressions containing spaces

It seems COMMAND_EXPAND_LISTS was indeed the key here. Thanks a lot! Yves On Mon, Apr 23, 2018 at 2:11 PM, CHEVRIER, Marc wrote: > The space is used to separate arguments passed to COMMAND. So your > generator expression is splitted before evaluation and elements are no

Re: [CMake] Generator expressions containing spaces

The space is used to separate arguments passed to COMMAND. So your generator expression is splitted before evaluation and elements are no longer valid generator expression. So, to solve your problem, encapsulate the generator expression inside quotes. And apply the following advices for

[CMake] Generator expressions containing spaces

Hi, I recently learned that the COMMAND line in a custom command supports generator expressions. In particular, what makes this powerful is that if the expression evaluates to the empty string, no corresponding code will be added to the target (as documented in the docs