Re: pkg-config "Requires" fields and propagated inputs

[Taylan Ulrich Bayırlı/Kammer]

address@hidden (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_ops.a and .la files in the $prefix/lib of that
package, but no .so files.  I'm not sure what this means.

>> ijs: pkg-config: () libs: ("ijs")
>> mesa: pkg-config: ("xcb-dri3" "xcb-dri2" "libudev" "xcb-dri3" "xcb-dri2") 
>> libs: ()
>> dbus-glib: pkg-config: ("gobject-2.0" "glib-2.0" "dbus-1") libs: ()
>> libcroco: pkg-config: ("libxml-2.0" "glib-2.0") libs: ()
>> gst-plugins-base: pkg-config: ("gio-2.0" "glib-2.0" "gio-2.0") libs: ()
>> harfbuzz: pkg-config: ("icu-uc") libs: ()
>> gtk+: pkg-config: ("gio-2.0" "cairo" "gio-2.0" "cairo" "gio-2.0" "cairo") 
>> libs: ()
>> pango: pkg-config: ("gobject-2.0" "glib-2.0" "gmodule-no-export-2.0" 
>> "fontconfig" "freetype2" "xft") libs: ()
>> cairo: pkg-config: ("xcb-shm" "xcb-render" "xcb-render") libs: ("z" "z")
>
> delete-duplicates?  :-)

Indeed.  Done.

> That looks nice.  So where’s the code?  ;-)

Here's the repo:

https://notabug.org/taylanub/guix

> What are your thoughts on how to integrate it?  Should we make a ‘lint’
> pass, or is there something that can be turned into a build phase?

It should be possible to make a build phase of it, using
'requires-and-libs-for-path' on the output directories, then using
'missing-packages' and 'missing-libraries' to find any pkg-config
packages, and libraries, which wouldn't be satisfied during use of the
package/output given its propagated inputs.

I'll try implementing this.

Taylan