On 2008-01-30 19:36-0700 Timothy M. Shead wrote:
[...]This produces expected results for all of the documented "boolean"
values: YES, NO, TRUE, FALSE, ON, OFF, etc. However, if I pass one of
those values to a macro:
macro(test var)
if(${var})
mes
Folks:
This seems like CMake 101, but I'm running into weird behavior testing
boolean expressions within a macro. I've reproduced the problem using
both 2.4.7 and CVS trunk on Gentoo Linux, presumably it is some subtlety
that I just don't get :)
If I run the following:
set(var YES)
On Jan 30, 2008 10:38 AM, Steven Van Ingelgem <[EMAIL PROTECTED]> wrote:
>
> I just thought that the "COMMAND" would be executed as is, and that
> VERBATIM meant there is no escaping... Hence my confusion
The docs say, "If VERBATIM is given then all the arguments to the
commands will be passed exa
Thanks for the explanation ;-). In fact that's what I am doing now:
${BASH} -c "..." which works nicely.
I just thought that the "COMMAND" would be executed as is, and that
VERBATIM meant there is no escaping... Hence my confusion
On 30/01/2008, Brad King <[EMAIL PROTECTED]> wrote:
> Steven Van
Steven Van Ingelgem wrote:
The problem in fact is in cmcommand.h @ line 67: "InvokeInitialPass"
Here there is done the pass through "ExpandArguments", which removes
the knowledge of the quoted/unquoted nature of the arguments... Before
is known if it's VERBATIM or not...
I think this is a deep
The problem in fact is in cmcommand.h @ line 67: "InvokeInitialPass"
Here there is done the pass through "ExpandArguments", which removes
the knowledge of the quoted/unquoted nature of the arguments... Before
is known if it's VERBATIM or not...
I think this is a deep problem, and rather difficult
Honest Guvnor wrote:
On Jan 29, 2008 6:21 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
Good Fortran support is relatively new to CMake. In fact, CVS CMake is
really the only version that handles all the Fortran depend stuff
reliably. CMake relies on the compiler to provide the correct run time
On Jan 29, 2008 6:21 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> Good Fortran support is relatively new to CMake. In fact, CVS CMake is
> really the only version that handles all the Fortran depend stuff
> reliably. CMake relies on the compiler to provide the correct run time
> libraries. If y
On Jan 29, 2008 6:19 PM, Andrew Brydon <[EMAIL PROTECTED]> wrote:
> I am dealing with a similar situation, and use the attached file.
>
> Tested with gnu fortran and absoft, but i believe adding other
> combinations to the
> KNOWN_FORTRAN_LIBRARIES
> variable should help.
>
> any feedback o
