Ah, thanks guys. STREQUAL does the trick. Sorry for the bother and lack
of quotes.
Jookia.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and
On Thu, Jul 21, 2011 at 1:44 AM, Michael Wild wrote:
> On 07/21/2011 07:07 AM, Jookia wrote:
> > Running the follow file causes problems:
> >
> > if(NOT "${CMAKE_BINARY_DIR}" MATCHES "${CMAKE_SOURCE_DIR}")
> > endif()
>
> MATCHES matches the LHS string against the regex on the RHS. Probab
On 07/21/2011 07:07 AM, Jookia wrote:
> Running the follow file causes problems:
>
> if(NOT "${CMAKE_BINARY_DIR}" MATCHES "${CMAKE_SOURCE_DIR}")
> endif()
MATCHES matches the LHS string against the regex on the RHS. Probably
you wanted to use STREQUAL instead.
Michael
___
Running the follow file causes problems:
if(NOT "${CMAKE_BINARY_DIR}" MATCHES "${CMAKE_SOURCE_DIR}")
endif()
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please k
On 7/20/2011 2:18 AM, Jookia wrote:
Greetings from the world of CMake problems,
I've been using CMake for a while (love it!) but a while back I sent my
project off to a person and he tried to generate the CMake project, but
it failed. Why? Because he for some reason keeps all his data in /s . So
Greetings from the world of CMake problems,
I've been using CMake for a while (love it!) but a while back I sent my
project off to a person and he tried to generate the CMake project, but
it failed. Why? Because he for some reason keeps all his data in /s . So
when CMake had the path /s/progra
