> --- Ursprüngliche Nachricht --- > Von: Brad King <[EMAIL PROTECTED]> > An: Alexander Neundorf <[EMAIL PROTECTED]> > Kopie: [email protected] > Betreff: Re: [CMake] bug or feature ? relative paths with > INCLUDE_DIRECTORIES() in cmake 2.4.1 > Datum: Fri, 12 May 2006 10:08:15 -0400 > > 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"? 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. Bye Alex
-- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
