Thread: BUG #1319: Windows LIB file libecpg.lib not in build or package
The following bug has been logged online: Bug reference: 1319 Logged by: Tom O'Connell Email address: toconnell@bphnx.com PostgreSQL version: 8.0 Beta Operating system: Windows 2000 Professional Description: Windows LIB file libecpg.lib not in build or package Details: The PostgreSQl version 8 BETA 4 package does not contain a libecpg.lib file. The build does not contain a Windows DEF file for libecpg. I was able to create the DEF file and LIB file for libecpg. I have run a few tests and the interface is working. A lib file is shipped in ..\lib\ms for the libpq interface.
Is there some problem with using ecpg on Win32? I was not aware of one. --------------------------------------------------------------------------- PostgreSQL Bugs List wrote: > > The following bug has been logged online: > > Bug reference: 1319 > Logged by: Tom O'Connell > > Email address: toconnell@bphnx.com > > PostgreSQL version: 8.0 Beta > > Operating system: Windows 2000 Professional > > Description: Windows LIB file libecpg.lib not in build or package > > Details: > > The PostgreSQl version 8 BETA 4 package does not contain a libecpg.lib file. > The build does not contain a Windows DEF file for libecpg. > > I was able to create the DEF file and LIB file for libecpg. I have run a > few tests and the interface is working. > > A lib file is shipped in ..\lib\ms for the libpq interface. > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
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? //Magnus > -----Original Message----- > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]=20 > Sent: Tuesday, November 30, 2004 8:49 PM > To: Tom O'Connell > Cc: pgsql-bugs@postgresql.org > Subject: Re: [BUGS] BUG #1319: Windows LIB file libecpg.lib=20 > not in build or package >=20 >=20 > Is there some problem with using ecpg on Win32? I was not=20 > aware of one. >=20 > -------------------------------------------------------------- > ------------- >=20 > PostgreSQL Bugs List wrote: > >=20 > > The following bug has been logged online: > >=20 > > Bug reference: 1319 > > Logged by: Tom O'Connell > >=20 > > Email address: toconnell@bphnx.com > >=20 > > PostgreSQL version: 8.0 Beta > >=20 > > Operating system: Windows 2000 Professional > >=20 > > Description: Windows LIB file libecpg.lib not in=20 > build or package > >=20 > > Details:=20 > >=20 > > The PostgreSQl version 8 BETA 4 package does not contain a=20 > libecpg.lib file.=20 > > The build does not contain a Windows DEF file for libecpg.=20=20=20 > >=20 > > I was able to create the DEF file and LIB file for libecpg. I have=20 > > run a few tests and the interface is working. > >=20 > > A lib file is shipped in ..\lib\ms for the libpq interface.=20=20 > >=20 > >=20 > > ---------------------------(end of=20 > > broadcast)--------------------------- > > TIP 5: Have you checked our extensive FAQ? > >=20 > > http://www.postgresql.org/docs/faqs/FAQ.html > >=20 >=20 > --=20 > Bruce Momjian | http://candle.pha.pa.us > pgman@candle.pha.pa.us | (610) 359-1001 > + If your life is a hard drive, | 13 Roberts Road > + Christ can be your backup. | Newtown Square,=20 > Pennsylvania 19073 >=20 > ---------------------------(end of=20 > broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >=20 >=20
Dave Page wrote:
>
>
> > -----Original Message-----
> > From: Magnus Hagander [mailto:mha@sollentuna.net]
> > Sent: 01 December 2004 09:21
> > To: Bruce Momjian; Tom O'Connell
> > Cc: pgsql-bugs@postgresql.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@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
=20 > -----Original Message----- > From: Magnus Hagander [mailto:mha@sollentuna.net]=20 > Sent: 01 December 2004 09:21 > To: Bruce Momjian; Tom O'Connell > Cc: pgsql-bugs@postgresql.org; Dave Page > Subject: RE: [BUGS] BUG #1319: Windows LIB file libecpg.lib=20 > not in build or package >=20 > AFAIK, we don't support ecpg with MSVC, only with MingW.=20 > Meaning it hasn't been verified to work. But it should be Ok=20 > to generate LIB files from the DLL and use those - just not=20 > tested. I don't see why it shouldn't work... >=20 > If it does work we should consider adding MSVC import=20 > libraries in the MSI build. Dave - we do this for some other=20 > package already, don't we? We do this for libpq.dll. I don't see why we cannot do libecpg as well. /D
Dave Page wrote: > > > > -----Original Message----- > > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] > > Sent: 01 December 2004 17:39 > > To: Dave Page > > Cc: Magnus Hagander; Tom O'Connell; pgsql-bugs@postgresql.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. Uh, why can we build psql and libpq fine? Can't we do the same for ecpg? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
=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.
=20 > -----Original Message----- > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]=20 > Sent: 01 December 2004 17:39 > 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 > > We do this for libpq.dll. I don't see why we cannot do=20 > libecpg as well. >=20 > Oh, ecpg is a library and a binary but it seems it might=20 > work. Added to > TODO: >=20 > * 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.