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

changed build system to accomodate name change of bacio library in bacio-2.5.0 release #592

Closed
wants to merge 1 commit into from

Conversation

edwardhartnett
Copy link
Collaborator

Fixes #589

In the bacio-2.5.0 release (Oct 20, 2021) the name of the bacio library and include directory change to no longer include the "_4".

In this PR I change the UFS_UTILS build to handle this. The version of bacio is checked in the top-level CMake file, and cmake variable bacio_name is set to either "bacio" or "bacio_4", depending on the bacio version. All other cmake files which use bacio have the name changed to ${bacio_name}.

I will add a github action which tests against the develop branch of bacio to ensure that UFS_UTILS keeps working with both old and new versions of the bacio library.

@edwardhartnett edwardhartnett changed the title changed for bacio name change changed build system to accomodate name change of bacio library in bacio-2.5.0 release Oct 21, 2021
@GeorgeGayno-NOAA
Copy link
Collaborator

@edwardhartnett We want to move UFS_UTILS from NOAA-EMC to ufs-community. To simplify the move, we don't want any open PRs. Can you close this, then reopen it after the move?

@GeorgeGayno-NOAA
Copy link
Collaborator

Temporarily close.

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.

handle bacio library name change with bacio-2.5.0 release
2 participants