Ancient is in the eye of the beholder. The CMake folks appear to take
backward compatibility seriously. You will appreciate this in ten
years when you revive a project that uses CMake.
Bill
On Fri, Jul 3, 2009 at 12:54 PM, Marcel Loose wrote:
> Wow,
>
> So this really is ancient code!
> Thanks f
Wow,
So this really is ancient code!
Thanks for the explanation.
Best regards,
Marcel Loose
On Fri, 2009-07-03 at 07:59 -0400, Brad King wrote:
> Eric Noulard wrote:
> >> If so, I still don't quite get the usage pattern in, e.g.,
> >> CheckIncludeFile.cmake. What are they trying to check?
> >
Eric Noulard wrote:
If so, I still don't quite get the usage pattern in, e.g.,
CheckIncludeFile.cmake. What are they trying to check?
Better ask the author of this file :-)
This was a hack left from before the 'DEFINED' option was
available from the if() command. The code
if(VAR MATCHES "
2009/7/2 Marcel Loose :
> Hi Eric,
>> The variable your are testing may contain "un-evaluated" var
>> or some special regex character( *, ?, ...)
>>
>> See attached example, you may test it with
>> $ cmake -P matches.cmake
>> MATCHES -- MYVAR = A good var
>> Look that one = double-dollar = blah /
Hi Eric,
On Wednesday 01 July 2009 18:28:57 Eric Noulard wrote:
> 2009/7/1 Marcel Loose :
> > Hi all,
> >
> > In a number of standard CMake modules I encountered the following line:
> >
> > IF("${VARIABLE}" MATCHES "^${VARIABLE}$")
> >
> > Can anyone explain the rationale of this conditional to m
2009/7/1 Marcel Loose :
> Hi all,
>
> In a number of standard CMake modules I encountered the following line:
>
> IF("${VARIABLE}" MATCHES "^${VARIABLE}$")
>
> Can anyone explain the rationale of this conditional to me.
The rational no but
> To my cluttered mind this seems to be an "always-
Hi all,
In a number of standard CMake modules I encountered the following line:
IF("${VARIABLE}" MATCHES "^${VARIABLE}$")
Can anyone explain the rationale of this conditional to me. To my
cluttered mind this seems to be an "always-true" condition.
Best regards,
Marcel Loose.
___