Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JCF: Issue #263: in dbt-workarea-env.sh, call spack load to put the d… #264

Merged
merged 2 commits into from
Mar 14, 2024

Conversation

jcfreeman2
Copy link
Collaborator

…esired CMake at the head of your path

@jcfreeman2 jcfreeman2 requested a review from andrewmogan March 14, 2024 17:07
@jcfreeman2
Copy link
Collaborator Author

Basically, the idea here is that no matter what, if you're in the base of a work area and you run dbt-workarea-env (or source its wrapper, . env.sh), you'll end up with CMake version 3.26.3, rather than quietly get stuck with CMake 3.23.1

@jcfreeman2 jcfreeman2 linked an issue Mar 14, 2024 that may be closed by this pull request
Copy link
Contributor

@andrewmogan andrewmogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested by running the following commands on np04 after cloning daq-buildtools and switching to this branch:

source /path/to/daq-buildtools/env.sh
dbt-create -n NFD_DEV_240314_A9 NFD_DEV_240314_A9
cd NFD_DEV_240314_A9
. env.sh
which cmake

which cmake outputs a very long path containing gcc-12.1.0/cmake-3.26.3-etc-etc

@andrewmogan andrewmogan merged commit 06b1755 into develop Mar 14, 2024
@andrewmogan andrewmogan deleted the johnfreeman/issue263_use_newer_cmake branch March 14, 2024 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get dbt-workarea-env to always give you our latest CMake version
2 participants