BUG #2585: Please provide pkg-config support

mafm@users.sourceforge.net wrote:

The following bug has been logged online:

Bug reference: 2585
Logged by:
Email address: mafm@users.sourceforge.net
PostgreSQL version: 8.1.4
Operating system: GNU/Linux
Description: Please provide pkg-config support
Details:

I haven't found a suitable place to put this wish-list item, and since most
projects manage these along with bug in trackers, here we go...

I'd like you to provide a pkg-config file, so people can use pkg-config to
gather the neccesary compiler flags to build and link against libpq
libraries.

whats wrong with using pg_config ?

Stefan

Well, I use around 10 libraries in my project, it's easier to use standardized
methods to gather the compiler/linker options using pkg-config than calling
different configuration scripts for each one, and using "pkg-config --exists
$name" or "pkg-config --at-least=1.0 $name" than to check whether
the "pg_config" script (and so with the rest) exists in your path, and
figuring out ways to compare versions. I was reporting it as a wish-list
item after all :)

Greetings.

On Monday 21 August 2006 16:44, Stefan Kaltenbrunner wrote:

mafm@users.sourceforge.net wrote:

The following bug has been logged online:

Bug reference: 2585
Logged by:
Email address: mafm@users.sourceforge.net
PostgreSQL version: 8.1.4
Operating system: GNU/Linux
Description: Please provide pkg-config support
Details:

I haven't found a suitable place to put this wish-list item, and since
most projects manage these along with bug in trackers, here we go...

I'd like you to provide a pkg-config file, so people can use pkg-config
to gather the neccesary compiler flags to build and link against libpq
libraries.

whats wrong with using pg_config ?

Stefan

--
Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>

Manuel A. Fernandez Montecelo wrote:

Well, I use around 10 libraries in my project, it's easier to use standardized
methods to gather the compiler/linker options using pkg-config than calling
different configuration scripts for each one, and using "pkg-config --exists
$name" or "pkg-config --at-least=1.0 $name" than to check whether
the "pg_config" script (and so with the rest) exists in your path, and
figuring out ways to compare versions. I was reporting it as a wish-list
item after all :)

Just FYI, this was proposed and rejected before. pg_config is our
method. It doesn't seem like too onerous a requeriment to change "pkg-"
to "pg_", is it?

The --at-least= or similar stuff may be useful though, not sure.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

[ redirecting to pgsql-hackers since this is not a bug ]

Alvaro Herrera <alvherre@commandprompt.com> writes:

Manuel A. Fernandez Montecelo wrote:

Well, I use around 10 libraries in my project, it's easier to use standardized
methods to gather the compiler/linker options using pkg-config than calling
different configuration scripts for each one,

Just FYI, this was proposed and rejected before. pg_config is our
method. It doesn't seem like too onerous a requeriment to change "pkg-"
to "pg_", is it?

The previous discussion starts here:
http://archives.postgresql.org/pgsql-patches/2004-08/msg00433.php

That requestor got off to an extremely bad start by presuming that
a documentation-free patch with no prior discussion would be a
sufficient way of proposing a new feature. However there are a
couple of pretty compelling points mentioned later in the thread,
particularly the issue of multiple installations on one machine.
(And does pkg-config still not distinguish CPPFLAGS from CFLAGS?)

Since that was two years ago, maybe we should take another look
and see if pkg-config has gotten better. If it hasn't evolved
some then the answer will probably be the same though.

regards, tom lane

Tom Lane wrote:

Since that was two years ago, maybe we should take another look
and see if pkg-config has gotten better. If it hasn't evolved
some then the answer will probably be the same though.

For all intents and purposes, pkg-config is still as broken as it ever
was. And I still haven't heard of a problem that it would solve that
we don't currently cover.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/