Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C common-superbuild
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • common-superbuild
  • Merge requests
  • !370

Fix ignored BOOST_ROOT when system CMake'ified Boost is available

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Bastien Jacquet requested to merge _transfer-keu/common-superbuild:SuperbuildBoostForceNoCmakeBoost into master Oct 22, 2020
  • Overview 2
  • Commits 1
  • Changes 1

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
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: SuperbuildBoostForceNoCmakeBoost