From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: pkg-config "Requires" fields and propagated inputs
Date: Sun, 03 May 2015 21:48:39 +0200 [thread overview]
Message-ID: <87mw1l1lyg.fsf@gnu.org> (raw)
In-Reply-To: <87fv7ieljt.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Wed, 29 Apr 2015 22:17:42 +0200")
taylanbayirli@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 output from my machine:
>
> 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?
> 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? :-)
That looks nice. So where’s the code? ;-)
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?
Thanks!
Ludo’.
next prev parent reply other threads:[~2015-05-03 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 20:48 pkg-config "Requires" fields and propagated inputs Taylan Ulrich Bayırlı/Kammer
2015-03-24 20:57 ` Ludovic Courtès
2015-03-24 22:52 ` Taylan Ulrich Bayırlı/Kammer
2015-03-25 16:56 ` Ludovic Courtès
2015-03-25 19:48 ` Taylan Ulrich Bayırlı/Kammer
2015-03-26 22:03 ` Taylan Ulrich Bayırlı/Kammer
2015-03-31 12:14 ` Ludovic Courtès
2015-04-29 20:17 ` Taylan Ulrich Bayırlı/Kammer
2015-05-03 19:48 ` Ludovic Courtès [this message]
2015-05-03 20:57 ` Taylan Ulrich Bayırlı/Kammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mw1l1lyg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).