Alexander Neundorf wrote:
Von: Brad King <[EMAIL PROTECTED]>
Alexander Neundorf wrote:
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.
This is now fixed in CVS CMake. It should be included in 2.4.3 but it
is too late for 2.4.2.
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"?
include_directories( bar/ )
->
would then add ${CMAKE_CURRENT_SOURCE_DIR}/bar/ and
${CMAKE_CURRENT_BINARY_DIR}/bar/
... it's just an idea, not sure it's a good one.
I don't think this is an obvious consequence of the name
"CMAKE_INCLUDE_CURRENT_DIR".
-Brad
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
