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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
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 17:39:17
Message-ID: 200412011739.iB1HdHY12474@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dave Page wrote:
>
>
> > -----Original Message-----
> > From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> > Sent: 01 December 2004 09:21
> > To: Bruce Momjian; Tom O'Connell
> > Cc: pgsql-bugs(at)postgresql(dot)org; Dave Page
> > Subject: RE: [BUGS] BUG #1319: Windows LIB file libecpg.lib
> > not in build or package
> >
> > AFAIK, we don't support ecpg with MSVC, only with MingW.
> > Meaning it hasn't been verified to work. But it should be Ok
> > to generate LIB files from the DLL and use those - just not
> > tested. I don't see why it shouldn't work...
> >
> > If it does work we should consider adding MSVC import
> > libraries in the MSI build. Dave - we do this for some other
> > package already, don't we?
>
> We do this for libpq.dll. I don't see why we cannot do libecpg as well.

Oh, ecpg is a library and a binary but it seems it might work. Added to
TODO:

* Allow ecpg to work with MSVC and BCC

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message postgresbugs 2004-12-01 19:58:46 Foreign keys referencing parent table fails on insert
Previous Message Tom Lane 2004-12-01 16:21:53 Re: BUG #1332: wrong results from age function