Open KrisThielemans opened 1 month ago
Actually, the 2nd option wouldn't help in my case. ITK distributes nifti include files with the original names, but the libraries are renamed to avoid conflicts (e.g. libITKniftiio-5.4.so).
Looks like ITK updated its nifti version here https://github.com/InsightSoftwareConsortium/ITK/commit/9c2c9fa9b8e8c83fd60fc09f7695990b33df4bb6, which was first incorporated in ITK 5.3 (released Nov 24, 2022), which is why we didn't see this before.
I have ITK 5.4 installed via conda, which installs a more recent version of the nifti library, see e.g. https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/ThirdParty/NIFTI/src/nifti/niftilib/nifti1.h and https://github.com/NIFTI-Imaging/nifti_clib/commits/master/niftilib/nifti1.h vs https://github.com/KCL-BMEIS/niftyreg/blob/master/reg-io/nifti/nifti1.h.
This causes problems when building our SIRF software that depends on both ITK and NiftyReg such as
There are a few ways to avoid version conflicts like this:
I suppose the 2nd option is the least painful.