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

Måns Rullgård mans
Thu Oct 23 10:38:27 CEST 2008

Reinhard Tartler <siretart at tauware.de> writes:

> M?ns Rullg?rd <mans at mansr.com> writes:
>> Luca Barbato <lu_zero at gentoo.org> writes:
>>> On 23-10-2008 0:36, M?ns Rullg?rd wrote:
>>>> Maybe you are too far gone to be saved, but I had to try my best.
>>>> I'll try one more time: what CFLAGS could you possibly need to pass
>>>> aside from a -I flag to indicate the location of the headers?
>>> -pthreads ?
>> That is not a standard flag.
> Putting arbitary additional information about what a library needs as
> you suggest is not standard but very toolchain specific as well.
> On the other hand using a tool that maintains that information
> externally [1] could take the used compiler into account and add some
> compatibilty glue. Sure, pkg-config might not do that today, however it
> seems to me that the approach of using an external tool instead of
> modifying all existing toolchains on this planet seems to me a more
> feasible solution.

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.

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), 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).

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list