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

AMReXBuildInfo.cmake: AMReX_DIR #3609

Merged

Conversation

ax3l
Copy link
Member

@ax3l ax3l commented Oct 26, 2023

Summary

The AMReX_DIR points if set to the CMake module path root.

The old logic did not work for me in a situation (ImpactX) where:

  • AMReX is pre-installed but
  • found through a superbuild of another transient lib (ABLASTR)

Additional background

Follow-up to #3599

Checklist

The proposed changes:

  • fix a bug or incorrect behavior in AMReX
  • add new capabilities to AMReX
  • changes answers in the test suite to more than roundoff level
  • are likely to significantly affect the results of downstream AMReX users
  • include documentation in the code and/or rst files, if appropriate

The `AMReX_DIR` points if set to the CMake module path root.

The old logic did not work for me in a situation where:
- AMReX is pre-installed but
- found through a superbuild of another transient lib (ABLASTR)
@ax3l
Copy link
Member Author

ax3l commented Oct 26, 2023

@WeiqunZhang Tested with WarpX and ImpactX. Does this also still work with MFIX?

@WeiqunZhang
Copy link
Member

Yes, it still works with MFIX's super and standalone builds.

@ax3l ax3l merged commit be6c641 into AMReX-Codes:development Oct 26, 2023
69 checks passed
@ax3l ax3l deleted the fix-buildinfo-script-superbuild-found branch October 26, 2023 16:50
guj pushed a commit to guj/amrex that referenced this pull request Dec 13, 2023
## Summary

The `AMReX_DIR` points if set to the CMake module path root.

The old logic did not work for me in a situation (ImpactX) where:
- AMReX is pre-installed but
- found through a superbuild of another transient lib (ABLASTR)

## Additional background

Follow-up to AMReX-Codes#3599

## Checklist

The proposed changes:
- [x] fix a bug or incorrect behavior in AMReX
- [ ] add new capabilities to AMReX
- [ ] changes answers in the test suite to more than roundoff level
- [ ] are likely to significantly affect the results of downstream AMReX
users
- [ ] include documentation in the code and/or rst files, if appropriate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants