From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Manuel A(dot) Fernandez Montecelo" <manuel(dot)montezelo(at)gmail(dot)com> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2585: Please provide pkg-config support |
Date: | 2006-08-22 18:57:54 |
Message-ID: | 20060822185754.GF25475@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-08-22 20:24:36 | Re: BUG #2585: Please provide pkg-config support |
Previous Message | Douglas Toltzman | 2006-08-22 18:37:56 | Re: BUG #2587: Connection problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-08-22 19:36:30 | Re: [HACKERS] COPY view |
Previous Message | Mark Dilger | 2006-08-22 18:56:17 | Re: An Idea for planner hints |