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:27:18 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C19@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 17:39
> 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
>
> > 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
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-12-01 20:34:31 | Re: BUG #1319: Windows LIB file libecpg.lib not in build or package |
Previous Message | Tom Lane | 2004-12-01 20:01:16 | Re: Ambiguous behaviour of age(timestamp) |