Re: [CMake] target_include_directories and relative paths inside generator expressions.

2014-04-24 Thread Andrew Fuller
On Thu, Apr 24, 2014 at 1:21 AM, Stephen Kelly wrote: > Andrew Fuller wrote: > > > It seems absolute paths are necessary. eg: > > > > target_include_directories( MyTarget PRIVATE > > $<$:${CMAKE_CURRENT_SOURCE_DIR}/some/dir> ) > > > > will perform as expected. > > > > Is this behaviour expected (

Re: [CMake] Explanation....

2014-04-24 Thread Matthew Woehlke
On 2014-04-24 04:53, Johannes Zarl wrote: On Wednesday, 23. April 2014, 18:54:39, Matthew Woehlke wrote: if (" ${arg}" STREQUAL " TOTO") set(" TOTO" "evil") You sure? When I checked, this did not work. Are *you* sure? :-) Also, the following gives me a syntax error: message( "${ foo}")

Re: [CMake] Explanation....

2014-04-24 Thread David Cole
> You sure? When I checked, this did not work. Also, the following > gives me a syntax error: > > set (" foo" "Evil!") > message( "${ foo}") But you *can* still do it indirectly (even with the 3.0 RCs): set (" variable with spaces" "Evil too!") set (varname " variable with spaces") m

Re: [CMake] Explanation....

2014-04-24 Thread Johannes Zarl
On Wednesday, 23. April 2014, 18:54:39, Matthew Woehlke wrote: > > if (" ${arg}" STREQUAL " TOTO") > > set(" TOTO" "evil") You sure? When I checked, this did not work. Also, the following gives me a syntax error: set (" foo" "Evil!") message( "${ foo}") Syntax error in cmake code at /hom

Re: [CMake] target_include_directories and relative paths inside generator expressions.

2014-04-24 Thread Stephen Kelly
Andrew Fuller wrote: > It seems absolute paths are necessary. eg: > > target_include_directories( MyTarget PRIVATE > $<$:${CMAKE_CURRENT_SOURCE_DIR}/some/dir> ) > > will perform as expected. > > Is this behaviour expected (and should be documented) or should I file a > bug? CMake doesn't know