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 E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C1A@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 20:35
> 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
> Uh, why can we build psql and libpq fine?  Can't we do the=20
> same for ecpg?

That's what we're trying to avoid though (using VC++ to compile). The
problem is the fact that mingw doesn't create VC++ compatible libraries,
so libecpg.lib cannot be used. All we need do though is create a VC++
import lib for libecpg.dll, and VC users should be fine. Unless they
want to static link of course.

I think we should continue to try to deprecate the VC/BCC builds, not
add to them - look at the trouble they've caused during this cycle for
example.

Regards, Dave.

pgsql-bugs by date:

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