| 1 |
On Fri, 31 Aug 2012 20:14:43 -0400 |
| 2 |
Alexis Ballier <aballier@g.o> wrote: |
| 3 |
|
| 4 |
> > Ah, while we're at it. If a library has macros referring |
| 5 |
> > to the functions of another library (or just types) in its public |
| 6 |
> > API, it needs a pkg-config file. ELF dependencies are not enough, |
| 7 |
> > and the gold linker will refuse to work because of a missing |
| 8 |
> > explicit dependency. |
| 9 |
> |
| 10 |
> Eh, straight to the point where pkgconfig is not the solution to |
| 11 |
> everything: a binary not using said macros but trusting pkgconfig will |
| 12 |
> get overlinked. Documentation stating that when using these |
| 13 |
> macros/functions one should link to the other lib would make things |
| 14 |
> even better. |
| 15 |
|
| 16 |
The macros/types can change over time. Maintaining all indirect |
| 17 |
dependencies is not friendly nor useful. |
| 18 |
|
| 19 |
-- |
| 20 |
Best regards, |
| 21 |
Michał Górny |
Archives