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 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’.