Re: [CMake] Replacing Compile Options for a Target

There's no problem as the compiler will just use the last flag value. See an example at http://coliru.stacked-crooked.com/a/738fff0fcc2eb3c4. Regards, Dvir Yitzchaki Debugger Software Engineer, SDT -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Jayesh

[Cmake-commits] CMake branch, master, updated. v3.7.1-765-gb620772

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20161206) +set(CMake_VERSION_PATCH 20161207) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] Replacing Compile Options for a Target

Hi, My global compile flags are specified with "std=c++14" in them. However, there is a third party header file which I want to compile in my code wherein I need to use a completely different set of compile flags starting with "-std=c++98". I have seen target_compile_options() but that seems

Re: [CMake] back-slashes for generator expression on windows

Check out the $ generator expression. See docs at the bottom of the following page: https://cmake.org/cmake/help/latest/manual/cmake-generator-expressions.7.html Something like $ should work I think. On Wed, Dec 7, 2016 at 8:30 AM, Bram de Jong wrote: >

[CMake] back-slashes for generator expression on windows

hi cmake-peoples! CMake v3.7.0: I'm using $ and $ on Windows and they generate paths with forward slashes... Is there an easy way to convert these to back-slashes? The testing tool (i.e. via add_test( ) ) I am using expects back-slashes... - Bram -- http://www.freesound.org

[Cmake-commits] CMake branch, next, updated. v3.7.1-1590-gd393492

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, next has been updated via d3934925a02995e97af78199d9ff04a57aa737d6 (commit) via

Re: [CMake] Prevent ExternalProject from updating git submodules

If you customize DOWNLOAD_COMMAND, you should also probably customize UPDATE_COMMAND. If you are just using a fixed snapshot from some repo, consider simply using a *.tar.gz snapped to that commit rather than connecting to the repo at all. The GitHub "/archive/" URLs are perfect for this.

[Cmake-commits] CMake branch, next, updated. v3.7.1-1534-g637c24b

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, next has been updated via 637c24bf527c7cf0ffc753a8fbe858e6b9a6fb35 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.1-764-g0f37cd2

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 0f37cd228e9668d981ff75f3e1c63d4f716b7e57 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.1-757-g22f05b1

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 22f05b1d8c8c52babe62ab44e6f1864aa73164a0 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.1-762-g0290bfc

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 0290bfc35dee73fb534556700554536f1164caaf (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.1-754-g9cf5fe2

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 9cf5fe22d0ac51a45d99823820a100ea02ab4305 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1528-ga966ea5

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, next has been updated via a966ea50fcd6425f74e3e6982b9548490a4acb8d (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1526-g7f9e152

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, next has been updated via 7f9e152943a1494fa784a86d7708dc6403a9a3d6 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1522-g258901c

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, next has been updated via 258901cd19d9bee049e65ae347536255b00fbe9d (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.1-1520-g860ad8e

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, next has been updated via 860ad8e96ac20c8fb77ee853b7c18b15db1747f1 (commit) via