[Cmake-commits] CMake branch, master, updated. v3.11.0-rc1-86-g1f082f2

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

[CMake] Adding a custom_command dependency to all sources

Howdy, I'm looking to add a dependency to all source files to ensure that a generated file is up-to-date before compilation. This generated file is "passed in" to the compiler via a global compiler definition. Is there an easy or built-in way to do this, or will I need to manually add a

Re: [CMake] Copying Shared Libraries (DLLs) Next to the Executable

Am 22. Februar 2018 04:20:40 MEZ schrieb "Marek Vojtko (Firaxis)" : >I was looking into GetPrerequisites and FixupBundle, but both of those >operate on an already existing executable and try to guess what shared >libraries (DLLs) it might need. It feels silly to guess

Re: [CMake] Copying Shared Libraries (DLLs) Next to the Executable

Personally, I find it much simpler just to expect the Path to include the locations of the DLL files as opposed to copying them. (And I often write small batch scripts to set up this development environment, and then optionally start cmake-gui.exe / devenv.exe / etc.) -- Daniel Schepler

[CMake] Building and exporting static and shared libs - best practice?

It's often useful to be able to make both static and shared varients of a library available to users of a package. My goal is to make the project cmake files as clean as possible, while supporting usage of either or both types of library by users. It should work from both build and installed

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc1-85-g020be37

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 020be379f4993cad5f2ca2066286f6f449b21f52 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc1-79-g8ac6c7e

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 8ac6c7e7f3234f4a2e5e4108114f173f16d4d388 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.0-rc1-9-g13c5a91

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, release has been updated via 13c5a91197dc99004e2c53864487aabdf09de936 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc1-77-g8d70cdd

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 8d70cddd223b9276ef05ad1a7f0094b3b1ed94c2 (commit) via