We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
this is more of a spack issue, but I wanted to document here b/c it was pothole on my adventure to use spack envs.
I noticed that many of our packages have custom rpath logic (compiler or machine specific) baked into the package.py.
Ideally we can provide this info via extra_rpaths when we setup a compiler in our spack environment.
extra_rpaths
But, if we use extra_rpaths - I don't think this logic is captured by the CMakeCachedPackage and I am not sure how to access it in a packages.py.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
this is more of a spack issue, but I wanted to document here b/c it was pothole on my adventure to use spack envs.
I noticed that many of our packages have custom rpath logic (compiler or machine specific) baked into the package.py.
Ideally we can provide this info via
extra_rpaths
when we setup a compiler in our spack environment.But, if we use
extra_rpaths
- I don't think this logic is captured by the CMakeCachedPackage and I am not sure how to access it in a packages.py.The text was updated successfully, but these errors were encountered: