l...@gnu.org (Ludovic Courtès) writes:
>> portaudio: pkg-config: () libs: ("asound")
>> avahi: pkg-config: ("glib-2.0" "gobject-2.0" "glib-2.0") libs: ()
>> libatomic-ops: pkg-config: () libs: ("atomic_ops")
>
> So ‘libs’ means that the .pc has “-latomic_ops”, right?
Indeed.
There are libatomic_
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
[...]
>> It looks like there are 3 classes of false positives here that would
>> need to be addressed to make the report more directly readable.
>
> I think all these false positives are fixed now!
Impressive!
> New sample outpu
Picking this topic back up after some things got in between:
l...@gnu.org (Ludovic Courtès) writes:
> taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
>
>> Maybe I should try to move to a strategy that calls pkg-config instead
>> of parsing the files in Guile, but it might be non
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
>
>> P.S.: I'll see if I can write a tool that compares the union of the
>> Requires[.private] fields of all .pc files in a package to the package's
>> propagated in
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
> P.S.: I'll see if I can write a tool that compares the union of the
> Requires[.private] fields of all .pc files in a package to the package's
> propagated inputs, so we can detect mismatches automatically.
So here's a first versi
l...@gnu.org (Ludovic Courtès) writes:
> taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
>
>> It might be nice to have build-only propagated inputs. On the other
>> hand, someone installing libxrandr in their profile will expect
>> pkg-config on libxrandr to work without errors.
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Do you have an example of a package that uses Requires.private?
>
> libxrandr is a good test case. Indeed I patched it a few days ago
> because some libraries in its Requires.private we
l...@gnu.org (Ludovic Courtès) writes:
> Do you have an example of a package that uses Requires.private?
libxrandr is a good test case. Indeed I patched it a few days ago
because some libraries in its Requires.private weren't propagated, which
fixed my issue.
>> However, pkg-config isn't aware
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> If I'm reading pkg-config documentation[0] right, Requires are full
> run-time dependencies, meaning if a program uses libfoo which Requires
> libbar, the program will also want/have to use libbar's interface; OTOH
> Requires.priv
I would appreciate it if someone helped me wrap my head around this.
Ideally I already got it and the following summary is correct; otherwise
please correct.
Pkg-config files (e.g. lib/pkgconfig/foo.pc for libfoo) may have a
"Requires" and a "Requires.private" field.
If I'm reading pkg-config doc
10 matches
Mail list logo
