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 B
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 t
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:
> hi cmake-peoples!
>
> CMake v3.7.0: I'
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
http://www.smartel
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.
However,