Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L LbNightlyTools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCb Core Software
  • LbNightlyTools
  • Issues
  • #99

Closed
Open
Created Sep 17, 2021 by Marco Clemencic@clemenciOwner

versions override are not correctly taken into account with new CMake configuration

New CMake configuration of projects do not fix the versions of the dependencies (at most there's a constraint on the minimum version), so CMake, by default, picks up the first compatible version it finds, which might not be the one we want to use for the slot.

For example, a slot configured to build LHCb/master on the released Gaudi/v35r4 is not built correctly as it picks up Gaudi v36r0 (the latest release at the moment).

Assignee
Assign to
Time tracking