-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UseITK upstream issue: ITK is added to the global include path #432
Comments
It turns out that we don't need `include(${ITK_USE_FILE})` in STIRConfig.cmake. This therefore avoids adding the ITK include directory to the global include path. Effectively fixes UCL#432 as when building STIR, we don't mind (currently anyway).
This can cause problems for SIRF etc or others who include STIR via CMake as the ITK include directory is therefore added to the global include path STIR/src/cmake/STIRConfig.cmake.in Line 82 in 6417022
Internally, we don't mind that the ITK include path added for all files (currently anyway). However, it turns out that we don't need |
It turns out that we don't need `include(${ITK_USE_FILE})` in STIRConfig.cmake. This therefore avoids adding the ITK include directory to the global include path. Effectively fixes UCL#432 as when building STIR, we don't mind (currently anyway).
- find_package Boost REQUIRED as its include files are needed - remove ITK_USE_FILE as not needed Fixes UCL#432
I've created an issue on ITK (InsightSoftwareConsortium/ITK#1450) flagging up the use of
include_directories
andlink_directories
inUseITK.cmake
.Can't imagine it'll be a quick fix (if at all), but we'll see what they say.
The text was updated successfully, but these errors were encountered: