-
Notifications
You must be signed in to change notification settings - Fork 2
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
CLHEP modulemap for CXXMODULES IB #5
Conversation
@oshadura , instead of adding it here which will endup in all our IBs, I would suggest to add it in to cms-sw/cmsdist rootmodule branch by creating a new spec e.g. cxxmodulemaps.spec . In future we can also add modulemaps for other external tools (e.g. boost etc.) |
If no objections then I can create the cxxmodulemaps.spec |
One of the advantages when having the module.modulemap as part of the package is that it will speed up builds with |
Before taking any action, I proposed @oshadura to replace the current modulemap with
which is more maintainable and should have the same effect. |
I would still suggest to add this in cmsdist (rootmodule branch) and update clhep.spec to deploy deploy it. e.g something like this in clhep.spec would work
this way overhead to manage this file for every clhep update will be less. |
all this is still in development, so I do not want to rebuild clhep for our production archs every other day because we want to update the modulemap. Once we have a working modoule map then I would suggest that we request to include it in upstream clhep repository instead of we patch it for every other version. |
cms-sw/cmsdist#5795 shall deploy clhep.modulemap in clhep/include directory now. |
@smuzaffar thank you so much! your and @vgvassilev solution is much more elegant 👍 |
I will close this PR in favor of your PR? |
cc: @davidlange6 @vgvassilev