Andrew Fuller wrote:
> It seems absolute paths are necessary. eg:
>
> target_include_directories( MyTarget PRIVATE
> $<$<PLATFORM_ID:Linux>:${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 at configure-time what the $<...> at the start of the
path will evaluate to at generate time (It could even be different things,
depending on the config).
I thought that would be obvious, but a patch to
Help/manual/cmake-buildsystem.7.rst
or
Help/command/target_include_directories.rst
might help.
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
