On Sat, 1 Sep 2012 09:40:47 +0200 Michał Górny <[email protected]> wrote:
> On Fri, 31 Aug 2012 20:14:43 -0400 > Alexis Ballier <[email protected]> wrote: > > > > Ah, while we're at it. If a library has macros referring > > > to the functions of another library (or just types) in its public > > > API, it needs a pkg-config file. ELF dependencies are not enough, > > > and the gold linker will refuse to work because of a missing > > > explicit dependency. > > > > Eh, straight to the point where pkgconfig is not the solution to > > everything: a binary not using said macros but trusting pkgconfig > > will get overlinked. Documentation stating that when using these > > macros/functions one should link to the other lib would make things > > even better. > > The macros/types can change over time. Maintaining all indirect > dependencies is not friendly nor useful. > So in this hypothetic case where your lib changes its ABI and API, it is not friendly and seen useless by consumers, I think I agree :)
