On 9-12-2012 14:05, Mark Morgan Lloyd wrote:
> Does Windows use the standard path for searching DLLs? I can confirm
> that inside a program temporarily changing the current directory has the
> desired effect, and this can obviously be done with reference to the
> registry.
For the authorative answ
On Sun, 9 Dec 2012, Mark Morgan Lloyd wrote:
Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Maybe the installer writes something in the registry, in which case you
could try that first.
There's a problem with this on (at least some versions of) Windows: if
you
Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Maybe the installer writes something in the registry, in which case you
could try that first.
There's a problem with this on (at least some versions of) Windows: if you
use InitialisePostgres3() it will find libpq.dll
Michael Van Canneyt wrote:
The reason that I ask is that it appears that the most efficient way
of getting libpq.dll for Windows is to install the ODBC drivers, and
they go into a directory typically named like C:\Program
Files\psql\ODBC\\bin where is a version number.
Maybe the ins
In our previous episode, Michael Van Canneyt said:
> >> Maybe the installer writes something in the registry, in which case you
> >> could try that first.
> >
> > There's a problem with this on (at least some versions of) Windows: if you
> > use InitialisePostgres3() it will find libpq.dll but no
On Sat, 8 Dec 2012, Mark Morgan Lloyd wrote:
Michael Van Canneyt wrote:
On Fri, 7 Dec 2012, Mark Morgan Lloyd wrote:
When using something like InitialisePostgres3(), if the approximate
location of the database library (.so or .dll) is known, what's the most
effective way of finding the exa
