[FFmpeg-devel] [PATCH] Use pkgconfig for dirac libs
Wed Oct 22 15:40:03 CEST 2008
On 22-10-2008 15:24, M?ns Rullg?rd wrote:
> Luca Barbato wrote:
>> On 22-10-2008 12:45, M?ns Rullg?rd wrote:
>>> Reinhard Tartler wrote:
>>>> M?ns Rullg?rd<mans at mansr.com> writes:
>>>>> In addition to that, it should be noted that pkgconfig doesn't
>>>>> actually work. It *lies* to you if you try to cross-compile.
>>>> In the attempt trying to add something constructive here, it seems that
>>>> pkg-config upstream is acknowledging the problem and considering changes
>>>> to improve the situation. At least according to:
>>> See, I was right all along. It *is* broken.
> So they're proposing to fix something they don't believe is broken?
> Doesn't that violate a commonly referred principle?
The short summary:
since set two environment variables could lead people to misuse our tool
we'll try to provide an option that is more in line with what's around
>>> Now if they'd only open
>>> their eyes to the simplest solution of all: stop using pkgconfig. I
>>> have never had a problem using libraries that *don't* use pkgconfig,
>>> so I have a hard time understanding what its purpose is.
>> Read what's there before pontificating...
> I still maintain there is no need for pkgconfig. To determine the utility
> of some tool X, one must ask whether X fixes something, not merely whether
> X breaks something. Some would argue that pkgconfig does not break anything,
> although I disagree. Be that as it may, I have to date not seen an actual
> example of something *fixed* by pkgconfig.
pkg-config just gives you a simple way to get certain informations about
libraries like version, cflags and ldflags needed to link and so on.
getting such informations w/out having to play guess games with gcc
usually quickens configure runs AND avoid headaches while crossbuilding
(since you don't have to override values you'd get otherwise just by
More information about the ffmpeg-devel