[FFmpeg-devel] [PATCH] Use pkgconfig for dirac libs

Måns Rullgård mans
Thu Oct 23 12:52:53 CEST 2008

Luca Barbato wrote:
> On 23-10-2008 10:38, M?ns Rullg?rd wrote:
>> Using separate files, and certainly files in an entirely different
>> directory, is fragile at best.  Your tool, pkgconfig or another, could
>> at the very least look inside the library archive for its data files.
>> Then there would be no risk of picking the wrong version.
> .pc file are put in $libdir/pkgconfig ...

As I said, different.  Additionally, pkgconfig searches according to
PKG_CONFIG_PATH (or similar), whilst the linker uses LIBRARY_PATH.
If these differ for whatever reason, you'll end up with a mismatch.

>> Furthermore, it is much less work to add a fairly trivial bit of code
>> to half a dozen linkers (and pkgconfig only works with gnu tools
>> anyway)
> and microsoft bad excuse for compiler (aka cl)...

Do I look like I care?  I'm talking about the native compilers on
various Unix systems and cross-compilers from non-gnu vendors.  These
are often much better than gcc.

>>, than it is to modify each and every package ever written to
>> use pkgconfig (even if we pretend for a moment that using it wasn't
>> associated with severe mental suffering).
> s/modify/replace at least 10 lines of cruft per dep with a single one
> iterable over a list/
> Please spend a bit of time checking...

Gentoo has well over 10000 packages.  If we want to add a feature to
10 linkers, it would take 1000 lines of code in each for this task to
match that of updating all packages.  I also believe that investing
a little more time, even 10 times more would acceptable, upfront in
fixing the root problem (static libs not recording dependencies) would
mean less work in the longer term.  This gives us 10000 lines of code
to implement the new linker feature, which I'm certain is more than
enough.  We must also not forget to take into account the burden of
writing and maintaining pkgconfig itself.

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list