Re: How to deal with static libraries and cmake?

Cristian Le via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> · Mon, 12 May 2025 10:09:13 +0200



      On
        2025/05/11 22:42, Orion Poplawski wrote:
      
        To
          be clear, I would prefer to be able to still package and ship
          the static libraries in a separate package.  Although I am
          considering just dropping the static build as well.  But I
          think the HPC / scientific community still has a reasonably
          high incidence so compiling statically.
          

      That
        would require upstream to have a compatible design, which is
        quite tricky to pull off and there are no CMake helpers that can
        ease the pain for that.
      If
        they are interested in supporting that they need to:
      
        separate
          the install(TARGETS)
          into different EXPORT
          sets for static and shared targets
        inside
          the Config.cmake file, read what COMPONENTS
          were requested (<PackageName>_FIND_COMPONENTS)
          and import either the shared or static targets (or both?)
      
      Supporting
        static library exports in CMake is complicated, particularly
        because you have to propagate private targets/dependencies as
        well. I wouldn’t recommend upstream to support static targets
        unless they have a good testing framework.
      &#8203;
    
  
-- 
_______________________________________________
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