Alexander Neundorf wrote:
The following CMakeLists.txt: include_directories( foo ${CMAKE_CURRENT_SOURCE_DIR}/bar) add_executable(hello main.c) produces the flags: gcc ... -I/home/alex/src/test/bar -Ifoo I would have expected that foo is also interpreted as relative to CMAKE_CURRENT_SOURCE_DIR, but apparently it isn't. Bug or feature ?
It's a bug. This is just another command that hasn't been coverted to interpret relative paths.
Maybe if the option CMAKE_ALWAYS_INCLUDE_CURRENT_DIR is enabled, it would also make sense to automatically add ${CMAKE_CURRENT_BINARY_DIR}/<the_relative_path> to the include path.
What is "the_relative_path"? -Brad _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
