Alexander Neundorf wrote:
Von: Brad King [EMAIL PROTECTED]
The idea of that option was to make *double-quote* includes look the
same for in-source and out-of-source builds. For angle-bracket
includes only the explicitly given include path should be used.
Note in your example that running
Hi,
recently cmake cvs has the new FILE() command:
FILE(SYSTEM_PATH ENVIRONMENT_VARIABLE _variable)
Now, there's the case that some tool outputs a list of directories (e.g.
kde-config), which will also contain the backward slashes. For use with
cmake the backslashes have to be replaced
Hello,
CMakeLists.txt:
SET( NAMESPACE vtk )
SET( ${NAMESPACE}_OPTION ON )
CONFIGURE_FILE( ${CMAKE_CURRENT_SOURCE_DIR}/foo.h.in
${CMAKE_CURRENT_BINARY_DIR}/foo.h @ONLY IMMEDIATE )
foo.h.in
#cmakedefine @[EMAIL PROTECTED]
This does not place the #define vtk_OPTION in foo.h. Replacing the
