From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200602120158.k1C1wUC12064@candle.pha.pa.us>
Subject: Re: Finding the pqlib version
In-Reply-To: <43EE7ACB.5060808@online.de>
To: Christoph Zwerschke <cito@online.de>
Date: Sat, 11 Feb 2006 20:58:30 -0500 (EST)
CC: pgsql-interfaces@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Christoph Zwerschke wrote:
> Bruce Momjian wrote:
>  > I was wondering that myself.  I am thinking you would need to use
>  > dlopen() to check for the symbol.  Because the libpq version could
>  > change after you compile, I can't see how you could make it a
>  > configure check unless you said you don't allow changes to libpq
>  > after the build.
> 
> The situation I was talking about is that you have a pre-compiled Python 
> and PostgreSQL installed on your system, together with their header 
> files, but you do not have the full source of Python and PostgreSQL 
> available. I want to be able to compile PyGreSQL as a Python extension 
> which is using functions from the python.dll and the libpq.dll, assuming 
> that the installed header files match the installed dlls.

Right, but assume you want to distribute that binary to others who might
have a different version of libpq.  This is required by packagers and a
run-time test is best in those cases.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073