Re: Development packages.
Roger Leigh <roger@whinlatter.uklinux.net> writes:
>> From what I can tell, the .pc files already contain enough information
>> to distinguish between direct and indirect dependencies.
>
> If you were to take libs specified in the .pc, and those directly
> Required by it, that should be the minimum.
>
> Better still, you could just take "pkg-config --libs", and then
> manually construct the dependency tree. You can then just include the
> root(s) of however many unique dependency trees you find.
>
> Since pkg-config is already an ELF executable, there's no reason why
> it can't do it directly when you use --libs. The only issue I see is
> distinguishing between normal (dynamic) linking and static linking
> (where the old behaviour is still required).
>
> Scott, if you do find the time to look at this, I would be ecstatic!
> If you don't have the time, I'll try to fit it in myself, since this
> is my main peeve with pkg-config.
>
>
Note that there is already a patch and bug report: #229980.
Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Python is executable pseudocode, Perl is executable line-noise.
Reply to: