[Top][All Lists]

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

Re: [EXTERNAL] Re: Q: library dependencies

From: Howard Chu
Subject: Re: [EXTERNAL] Re: Q: library dependencies
Date: Fri, 25 Sep 2020 19:23:58 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.3

Bob Friesenhahn wrote:

> ... static libraries do not technically have "dependencies" since they only 
> represent a compilation step (no linking).  If a static
> library may also be built as a shared library then it may have dependencies 
> and should be described as such.

I've always found this distinction ridiculously annoying. A program/project 
that links perfectly
fine when its explicitly listed dependencies are shared libraries suddenly 
fails to link when
you change to using -static. It's also simple to remedy - just list the 
dependencies inside a
member of the archive file.

Please consider this thread and adopting the feature implemented there:

> The final shared library or program itself surely has "dependencies" since 
> otherwise it might not successfully link due to unresolved symbols.

  -- Howard Chu
  CTO, Symas Corp. 
  Director, Highland Sun
  Chief Architect, OpenLDAP

reply via email to

[Prev in Thread] Current Thread [Next in Thread]