-
Couldn't load subscription status.
- Fork 38
Differentiate between lib and lib64 in modules #154
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
Differentiate between lib and lib64 in modules #154
Conversation
|
I like the changes. |
Check if building MPI, compiler, or CMake and if so don't run configure_file on module Move CMake script into generate file
|
@aerorahul I added a check if building |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good.
You will need to bring you branch up to date before CI and merge.
|
|
||
| # Install the module with configure_file, replacing ${CMAKE_INSTALL_LIBDIR} (and potentially other variables) | ||
| # with the actual value for that system | ||
| $SUDO cmake -DCMAKE_INSTALL_LIBDIR=${CMAKE_INSTALL_LIBDIR} \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good.
I would just note that we will need more template variables e.g. PYTHON_VERSION in bufr.lua.
We can address that in a later PR.
Instead of hardcoding
lib, make it a templated value and at module installation detectCMAKE_INSTALL_LIBDIRand fill it into the module usingconfigure_file.