Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lcgcmake
Manage
Activity
Members
Labels
Plan
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
sft
lcgcmake
Commits
311b6bf0
Commit
311b6bf0
authored
6 months ago
by
Andre Sailer
Browse files
Options
Downloads
Patches
Plain Diff
SPI-2635
: update boost to 1.86 in dev4
parent
29dee017
No related branches found
No related tags found
1 merge request
!2440
SPI-2635: update boost to 1.86 in dev4
Pipeline
#7966310
passed
6 months ago
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cmake/toolchain/heptools-dev4.cmake
+1
-6
1 addition, 6 deletions
cmake/toolchain/heptools-dev4.cmake
with
1 addition
and
6 deletions
cmake/toolchain/heptools-dev4.cmake
+
1
−
6
View file @
311b6bf0
...
...
@@ -8,12 +8,7 @@ include(heptools-dev-generators)
#LCG_external_package(ROOT v6-32-00-patches GIT=http://root.cern.ch/git/root.git)
LCG_AA_project
(
ROOT 6.32.04
)
# Add Boost 1.84.0 for testing on dev4
#if((${LCG_COMP} MATCHES gcc AND ${LCG_COMPVERS} GREATER 8) OR (${LCG_COMP} MATCHES clang AND ${LCG_COMPVERS} GREATER 12))
# LCG_external_package(Boost 1.84.0 )
#else()
# LCG_external_package(Boost 1.78.0 )
#endif()
LCG_external_package
(
Boost 1.86.0
)
#if(${LCG_OS}${LCG_OSVERS} MATCHES centos|ubuntu|el)
# if(((${LCG_COMP} MATCHES gcc) AND (${LCG_COMPVERS} GREATER 7)) OR (${LCG_COMP} MATCHES clang))
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment