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

[Måns Rullgård]

Diego 'Flameeyes' Petten? wrote:
> M?ns Rullg?rd <mans at mansr.com> writes:
>
>>> Uh? May I ask what tool is building /usr/arm-unknown-linux-gnueabi tree
>>> then? I'm sure enough that the (scarse) Gentoo crosscompiling supports
>>> generate proper .pc files that _don't_ point to /usr/lib so I'd be ready
>>> to expect a bug in some build tool that prepares that root...
>>
>> I use Gentoo, following the instructions to the letter.  No problems at
>> all with non-pkgconfig packages...
>
> Hrm, I have to check the cross-compiling support again since I'm sure it
> worked flawlessy last time I did this type of work.
>
>>> A properly-configured pkg-config executable shouldn't send it anywhere;
>>> standard non-crosscompiling pkg-config never returns -I/usr/include or
>>> -L/usr/lib (or -L/usr/lib64 on amd64 multilib systems); a
>>> properly-configured crosscompiling pkg-config will do the same...
>>
>> Does such a thing exist?  The link Reinhard posted suggests that it does
>> not.
>
> Well, I used a modified pkg-config ebuild at the time (which I should

That implies that it didn't work properly, contradictory to what you said
above.

> still have laying around, if I I find it I'll see to merge in the recent
> changes and see that it gets into main tree), ut I don't remember
> needing to change the source code at all. So unless they broke it
> recently (which I wouldn't exclude) I'd expect it to work.
>
> [I have routing troubles right now so I'm unable to access fd.o, I'll
> call my ISP and doublecheck.]
>
> But I remember not having to fight with pkg-config, and rather saved me
> more time than other things did, like libtool. (Which by the way reminds
> me I have to push again for the dependency information to be properly
> spilt).

To avoid any misunderstanding, libtools causes much more trouble than
pkgconfig, probably because it is more widely "used".  It also does
its best to send the linker looking in /usr/lib, inevitably resulting
in link failures.  The only workaround I've found is to edit all the
installed .la files, and edit the libtool script, that each and every
package insists on shipping, removing the line where it *always* adds
-L/usr/lib, no matter what.

> I don't think I have my last build environment around, but I should have
> the script to regenerate it, I'll check if there are regressions in
> there; I had to leave this in my TODO list for too long time :/

If you can fix, that would be much appreciated, not only by me.

-- 
M?ns Rullg?rd
mans at mansr.com