RPM Community Forums

Mailing List Message of <popt-devel>

Re: [PATCH] added pkgconfig support for popt

From: Jeff Johnson <n3npq@mac.com>
Date: Sat 25 Jul 2009 - 07:39:22 CEST
Message-id: <972A147F-AABC-43E5-AC34-14637460AA20@mac.com>

On Jul 21, 2009, at 11:21 AM, devzero2000 wrote:

> Very thiny patch for integrating pkg-config(1) support for popt
> library into popt itself.
>

Sorry for the delay.

I applied the pkgconfig patch with these changes:

1) I'd rather see "popt.pc", not "libpopt-@VERSION@.pc". That's
consistent with "neon.pc", another library used widely where
version makes a difference. It also seems kinda silly to add
pkgconfig functionality to discover popt's version with the version
in the *.pc file name itself.

2) popt is strange in that it typically installs (on linux) into /lib  
or /lib64
rather than into $(libdir). Which means I had to use this construct
in Makefile.am (which likely breaks with multilib):
    pkgconfigdir = $(prefix)/lib/pkgconfig
    pkgconfig_DATA = popt.pc
and this construct in popt.spec (which likely works with multlib)
    %{_prefix}/%{_lib}/pkgconfig/libpopt-%{version}.pc
lest popt become the very first and only package to start populating
/lib/pkconfig/*, or the first/only per-arch package that installs
into /usr/share/pkgconfig. I _REALLY_ wish not to break new
ground.

Transitive install option discovery is of course mostly insane if/when  
pkgconfig
has a different prefix than $(libdir): if you know where to put  
"popt.pc" when
building popt (alternatively how to configure pkgconfig differently  
than default
--libdir), then you also know both of these datum-di-dums:

     Libs: -L${libdir} -lpopt
     Cflags: -I${includedir}

But hey, whatever needs to be done to avoid the endless bikeshed  
discussions
about --prefix and The One True Way To Build Software.

w00t! popt uses pkgconfig!

73 de Jeff




Received on Sat Jul 25 07:40:01 2009
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.