Re: BUG #1319: Windows LIB file libecpg.lib not in build or package
| От | Bruce Momjian |
|---|---|
| Тема | Re: BUG #1319: Windows LIB file libecpg.lib not in build or package |
| Дата | |
| Msg-id | 200412012034.iB1KYV611331@candle.pha.pa.us обсуждение исходный текст |
| Ответ на | BUG #1319: Windows LIB file libecpg.lib not in build or package ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>) |
| Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: