Re: BUG #1319: Windows LIB file libecpg.lib not in build or package - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #1319: Windows LIB file libecpg.lib not in build or package
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C19@ratbert.vale-housing.co.uk
Whole thread Raw
In response to BUG #1319: Windows LIB file libecpg.lib not in build or package  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List pgsql-bugs
=20

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]=20
> Sent: 01 December 2004 17:39
> To: Dave Page
> Cc: Magnus Hagander; Tom O'Connell; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1319: Windows LIB file libecpg.lib=20
> not in build or package
>=20
> > We do this for libpq.dll. I don't see why we cannot do=20
> libecpg as well.
>=20
> Oh, ecpg is a library and a binary but it seems it might=20
> work.  Added to
> TODO:
>=20
>     * Allow ecpg to work with MSVC and BCC

The .exe should be OK with VC++ at least - even in the GUI you can
create custom build steps easily enough. There is no reason why an
import lib cannot be created - in fact, I'll do so in a minute and add
it to pginstaller.

Of course, it would be nice to generate these libs as part of the main
build process, but I don't believe that is possible without VC++, so
it'll probably have to remain an installer extra.

Regards, Dave.

pgsql-bugs by date:

Previous
From: "Dave Page"
Date:
Subject: Re: BUG #1319: Windows LIB file libecpg.lib not in build or package
Next
From: Neil Conway
Date:
Subject: Re: oid2name core dump