Previous versions of STIR wrote files in ${CMAKE_INSTALL_PREFIX}/include/stir and ${CMAKE_INSTALL_PREFIX}/lib/cmake/STIR*cmake. STIR 6.0 writes them in version specific folders https://github.com/UCL/STIR/pull/1358. However, an existing config of SIRF seems to still find the old ones. This can be resolved by (for instance on the VM)
cd ~/devel/install
rm -rf include/stir
rm -f lib/STIR*.cmake
before updateVM.sh.
We could add this to the UPDATE.sh script, or point users to this in the doc (although who reads that?)
In fact, we're going to have lots of problems like this, so I suggest to nuke ~/devel/install as well as ~/devel/buildVM/builds/.
Previous versions of STIR wrote files in
${CMAKE_INSTALL_PREFIX}/include/stir
and${CMAKE_INSTALL_PREFIX}/lib/cmake/STIR*cmake
. STIR 6.0 writes them in version specific folders https://github.com/UCL/STIR/pull/1358. However, an existing config of SIRF seems to still find the old ones. This can be resolved by (for instance on the VM)before
updateVM.sh
.We could add this to the
UPDATE.sh
script, or point users to this in the doc (although who reads that?)In fact, we're going to have lots of problems like this, so I suggest to nuke
~/devel/install
as well as~/devel/buildVM/builds/
.@casperdcl @paskino what do you think?