> Have you tried quotes in your message() so it doesn't remove the semi-colons?
> message("${x}")
ah, that explains my confusion of the missing semi-colon
thanks, tim
--
t...@klingt.org
http://tim.klingt.org
Relying on the government to protect your privacy is like asking a
peeping tom to inst
On Tuesday, March 15, 2011 10:25:17 am Tim Blechmann wrote:
> hi all,
>
> i am trying to write a ctest script, compiling for different OSX
> architectures. the CMAKE_OSX_ARCHITECTURES option uses the semicolon to
> distinguish between architectures, but my attempts to generate the
> argument strin
What are you going to do with it once it's in the value ARCH or x?
It's hard to see the literal contents of a cmake variable without
using "" in the message command.
This code:
set(x "-DCMAKE_OSX_ARCHITECTURES=i386\\;x86_64")
message("${x}")
produces this output:
-DCMAKE_OSX_ARCHITECTURES=i386\;
hi all,
i am trying to write a ctest script, compiling for different OSX architectures.
the CMAKE_OSX_ARCHITECTURES option uses the semicolon to distinguish between
architectures, but my attempts to generate the argument string with semicolons
haven't been successful, it seems they are not esca
