From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom O'Connell" <toconnell(at)bphnx(dot)com> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #1319: Windows LIB file libecpg.lib not in build or package |
Date: | 2004-12-01 13:22:43 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C08@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> -----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.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom O'Connell | 2004-12-01 13:26:29 | Re: BUG #1319: Windows LIB file libecpg.lib not in build o |
Previous Message | simon | 2004-12-01 13:08:04 | Re: BUG #1335: Wrong sort result in union queries |