[Insight-developers] Wrapping Woes -- And a fix
Hans Johnson
hans-johnson at uiowa.edu
Wed Jun 1 22:12:09 EDT 2005
Hello CableSwig Maintainers,
I have been having problems with building CableSwig itself. It turns out
that the include paths used for building CableSwig are added to then end of
the ITK include paths. This causes problems when the ITK include paths
point to a directory that contains a file named the same as one CableSwig
requires from its own directory (i.e. "config.h" was my culprit).
I have solved the problem by simply adding BEFORE flag to the
INCLUDE_DIRECTORIES commands in a few of the CableSwig CmakeLists files. It
may be prudent to do this to all the INCLUDE_DIRECTORIES commands for
CableSwig.
I've listed diffs to the main tree below:
Hans
Index: CMakeLists.txt
===================================================================
RCS file: /cvsroot/CableSwig/CableSwig/CMakeLists.txt,v
retrieving revision 1.18
diff -r1.18 CMakeLists.txt
48c48
< INCLUDE_DIRECTORIES(
---
> INCLUDE_DIRECTORIES(BEFORE
Index: GCC/gcc/CMakeLists.txt
===================================================================
RCS file: /cvsroot/CableSwig/CableSwig/GCC/gcc/CMakeLists.txt,v
retrieving revision 1.10
diff -r1.10 CMakeLists.txt
4c4
< INCLUDE_DIRECTORIES(
---
> INCLUDE_DIRECTORIES( BEFORE
Index: GCC/libiberty/CMakeLists.txt
===================================================================
RCS file: /cvsroot/CableSwig/CableSwig/GCC/libiberty/CMakeLists.txt,v
retrieving revision 1.2
diff -r1.2 CMakeLists.txt
2,3c2,3
< INCLUDE_DIRECTORIES(${GCC_SOURCE_DIR}/include)
< INCLUDE_DIRECTORIES(${GCC_BINARY_DIR}/libiberty)
---
> INCLUDE_DIRECTORIES(BEFORE ${GCC_SOURCE_DIR}/include)
> INCLUDE_DIRECTORIES(BEFORE ${GCC_BINARY_DIR}/libiberty)
More information about the Insight-developers
mailing list