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
add INSTALL_STATIC_LIBS buid option #2071
Conversation
to allow to not install the static library
@remicollet |
This has to be managed upstream in the CMakeLists else the installed Downstream (packaging) can remove the *.a file (a common practice), but cmake will have to be fixed, so this new option is really the simple way, have cmake generate the proper file. Of course, this patch can be used "only" for packaging, but as it has no impact in standard build... and other distros may need them... and I hate having not upstreamable patch... |
It was incorrect optimization. Existing build script always creates static library. If BUILD_SHARED_LIBS is ON it repackages static library into shared library. I will rollback it so that BUILD_SHARED_LIBS does not install static library |
You may be right though ... An INSTALL may be better approach |
Thanks (and indeed version 0.16.x was OK) |
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #2071 +/- ##
=======================================
Coverage 83.48% 83.49%
=======================================
Files 159 159
Lines 31957 31957
=======================================
+ Hits 26679 26681 +2
+ Misses 5278 5276 -2 ☔ View full report in Codecov by Sentry. |
@maxirmx can you help approve if good to go? Thanks. |
@ronaldtse please give me a day to think. @remicollet made a perfectly valid point about packaging. There are three options how to fix it. We shall consider both downstream requirements and CI performance. We are now running ~110 test workflows and adding a flag can bring it up to 150. |
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.
I propose to rollback to the previous algorithm -- #2076
It means double run for installation/packaging if both libraries are needed but it loooks like there are no complains
to allow to not install the static library
As RPM packaging Guidelines disallow static libraries
See https://docs.fedoraproject.org/en-US/packaging-guidelines/#packaging-static-libraries