Did you try with $ rather than the ; character?
Le dim. 3 juin 2018 à 06:24, Craig Scott a écrit :
> On Sun, Jun 3, 2018 at 12:34 PM, Neil Carlson
> wrote:
>
>> On Sat, Jun 2, 2018 at 4:53 PM Stephen McDowell
>> wrote:
>>
>>> It should be a CMake list, which is delineated by semicolons.
>>>
>>
On Sun, Jun 3, 2018 at 12:34 PM, Neil Carlson
wrote:
> On Sat, Jun 2, 2018 at 4:53 PM Stephen McDowell
> wrote:
>
>> It should be a CMake list, which is delineated by semicolons.
>>
>> add_compile_options($<$-Wall;-Wextra>)
>>
>> I am writing this from a phone so untested, but that has worked fo
On Sat, Jun 2, 2018 at 4:53 PM Stephen McDowell wrote:
> It should be a CMake list, which is delineated by semicolons.
>
> add_compile_options($<$-Wall;-Wextra>)
>
> I am writing this from a phone so untested, but that has worked for me in
> the past.
>
Right about the list, and is one of the th
It should be a CMake list, which is delineated by semicolons.
add_compile_options($<$-Wall;-Wextra>)
I am writing this from a phone so untested, but that has worked for me in
the past.
-Stephen
On Sat, Jun 2, 2018, 3:47 PM Neil Carlson wrote:
> I'm attempting to use a generator expression to
I'm attempting to use a generator expression to conditionally add compile
options. No problem if it is a single option, but I can't figure out how to
manage multiple options (in a single command).
For example, this works:
add_compile_options($<$-Wall>)
As does this:
add_compile_options(-Wall -Wex
Hi,
I also found that e.g. Qt Creator throws away the cache too eagerly, e.g. when
changing the deployment target IP address on the kit.
This led me to finding a solution for keeping command line definitions
elsewhere because relying on the cache will hurt you bad sometimes.
Maybe more projec
You can easily avoid this bad experience by using different builds
environments : one per compiler !
Le sam. 2 juin 2018 à 11:43, René J.V. Bertin a
écrit :
> Hi,
>
> This happened once too often for me: I apply successive tweaks to a
> CMakeCache file, reinvoke make (or ninja) and then at some p
Hi,
This happened once too often for me: I apply successive tweaks to a CMakeCache
file, reinvoke make (or ninja) and then at some point lose everything because I
forgot that changing the compiler is a "lethal" operation.
Why does cmake have to throw away the entire cache file when something ch
