On 2/22/22 19:47, Kevin Kofler via devel wrote: > Denis Fateyev wrote: >> The "ustl" upstream, for which I maintain the RPM package, has recently >> switched from providing a shared library to a static library. > > Generally, you do not want to follow such a change, but force the build > system to build a shared library instead, even if it is not the upstream > default. > > Kevin Kofler Would uSockets be an exception? That is designed to be used as a static library with link-time optimization, so that trivial functions (such as struct getters) can be inlined into users of the library. Not doing so is (according to their documentation) a huge performance hit. That said, should such a library just be shipped as source code? -- Sincerely, Demi Marie Obenour (she/her/hers)
Attachment:
OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
