Re: CVS Commit by dpage: Dynamically link libpq/OpenSSL for sensible

> -----Original Message-----
> From: Alexander Borkowski
> [mailto:alexander(dot)borkowski(at)abri(dot)une(dot)edu(dot)au]
> Sent: 07 October 2004 08:23
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] CVS Commit by dpage:
> Dynamically link libpq/OpenSSL for sensible
>
> Dave Page wrote:
>
> > No, they need to be there - there the import libraries that
> contain the stubs for the functions in the dlls.
>
> Please correct me if I get this totally confused, but aren't
> the stubs for the SSL stuff already in libpq.dll (looking at
> postgresql-8.0.0beta3/src/interfaces/libpq/win32.mak with
> USE_SSL defined)? And as far as I can tell pgAdmin III is not
> using any of the SSL functions directly anyway since they are
> hidden behind the libpq API (pgConn.cpp lines 196 to 207), so
> why link against the SSL libraries (static or dynamic) in this case?

Ahh, no you're right. There was an SSL call in pgAdmin, but that's gone
now. I've added it to my todo.

Regards, Dave.