more artifact information in local scope #296
Replies: 2 comments
-
Hey @sbowman-mitre! Thanks for the kind feedback and suggestion! I see how the info can be useful. In case you haven't seen it already, CPM.cmake currently stores the version for all dependencies that can be retrieved using Not sure if it's helpful to you, but we do create some files in the build directory which you could use to restore the original args. Specifically, in |
Beta Was this translation helpful? Give feedback.
-
I'll look also at Thank you! 👍 |
Beta Was this translation helpful? Give feedback.
-
Hi, I love CPM 💯 and have started using it pervasively in my cmake projects. It has made such an improvement to my build descriptions and I have so much added control over my dependency map. Thank you!
I do have a feature request: add extra descriptive variables to local scope for each CPMAddPackage() call. Currently, you provide:
For my build processes, I'd also like:
Basically, a local scope repeat of the inputs when CPMAddPackage() was called. That would allow my build processes to report the versions of dependencies that were defined in the build. There is a possible work-around, but it is awkward and I'd like your ideas. Should I add this as a new issue? Or do you have a recommendation for how to do this that I should try?
Beta Was this translation helpful? Give feedback.
All reactions