Re: How to deal with static libraries and cmake?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 10 May 2025 05:42:07 CEST, Orion Poplawski <orion@xxxxxxxx> wrote:

>  * The installation package was faulty and contained
>
>     "/usr/lib64/cmake/SuiteSparse_config/SuiteSparse_configTargets.cmake"
>
>  but not all the files it references.
>
>
>Is there some way that packages can handle having the static libs not be present in a general way?  I'd like to avoid having to do separate shared and static builds.
>

A simple/generic way to do this, unfortunately no. It is a case-by-case basis.

A minimum patch is to find the `install(TARGETS)` commands that mention the static target (directly or indirectly from an expanded list variable) and remove it.

Long term solution is to ask upstream to support optional static library build and/or incremental build+installation. You can ping me upstream if they have issues supporting that.
-- 
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux