Fix ignored BOOST_ROOT when system CMake'ified Boost is available (!370) · Merge requests · ParaView / common-superbuild

Open Bastien Jacquet requested to merge _transfer-keu/common-superbuild:SuperbuildBoostForceNoCmakeBoost into master Oct 22, 2020

If a CMake'ified Boost (providing a BoostConfig.cmake) is available in CMake search paths (which is the default of Ubuntu 20.04), it will always be the one found, even if BOOST_ROOT and/or NO_SYSTEM_BOOST_PATH is set.

We need to manually add Boost_No_CMake_Boost=1 together with BOOST_ROOT:PATH=<INSTALL_DIR> to keep the previous behavior in cases where the common-superbuild is building Boost.

Found by @julia.sanchez with Ubuntu 20.04, while compiling LidarView which uses the common-superbuild provided Boost project

Closes #53

Edited Oct 22, 2020 by Bastien Jacquet