Re: BUG #1319: Windows LIB file libecpg.lib not in build or package

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Tom O'Connell" <toconnell(at)bphnx(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #1319: Windows LIB file libecpg.lib not in build or package
Date: 2004-12-01 20:40:58
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C1A@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: 01 December 2004 20:35
> To: Dave Page
> Cc: Magnus Hagander; Tom O'Connell; pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] BUG #1319: Windows LIB file libecpg.lib
> not in build or package
>
> Uh, why can we build psql and libpq fine? Can't we do the
> 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.

Browse pgsql-bugs by date

  From Date Subject
Next Message Oliver Elphick 2004-12-01 21:20:16 [Fwd: Bug#283856: postgresql: mistakes in src/backend/po/fr.po]
Previous Message Bruce Momjian 2004-12-01 20:34:31 Re: BUG #1319: Windows LIB file libecpg.lib not in build or package