I’m trying to compile ITK with the remote module RTK and python wrapping.
I’m having issues with building the RTK python wrapper with multiple symbol definition on Windows, I tried tackling it to no avail. In the meantime, I would like to just disable the python wrapping of RTK for now.
So my current setup is, Windows x64, MSVS 2019. I’m building ITK as part of my cmake project. ITK is being built as an ExternalProject_Add using the ninja generator.
@eric what are the complete parameters for ITK’s ExternalProject_Add? Does a clean build help, i.e. delete the build directory then re-run with -DRTK_WRAP_PYTHON=OFF?
Sorry no. I never use the option RTK_WRAP_PYTHON. Why not just disabling RTK in a separate build for the wrappings only?
The Windows wrapping seems to build fine on the CI, can you report your issue on RTK’s github please?
@dzenanz
I will try that again. I initially had it as a CMAKE_CACHE_ARG and I tried it, but no luck. I hadn’t tried it with the RTK_WRAP_PYTHON as a CMAKE_ARG. I don’t know if it can make a difference using CMAKE_CACHE_ARG vs CMAKE_ARG.
@simon.rit
There is an issue already opened for this.
It’s issue #351.
It probably builds on the CI correctly because it’s not wrapping the CUDA objects
For your suggestion about compiling the wrapping separately, is there a smart way of doing it?
My understanding is to compile itk 2 times: once with RTK and no python wrapping, and a second time with the python wrapping, but without RTK. Is that correct? And in my specific case, I would need to have 2 separate ExternalProject_Add config