Re: pg_config MSVC makefile
От | Dave Page |
---|---|
Тема | Re: pg_config MSVC makefile |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4528282@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | pg_config MSVC makefile (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: pg_config MSVC makefile
|
Список | pgsql-patches |
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 07 January 2005 16:25 > To: Bruce Momjian > Cc: Dave Page; Andrew Dunstan; Patches (PostgreSQL) > Subject: Re: [PATCHES] pg_config MSVC makefile > > > > more of a pain. If people are submitting patches it means they are > > using them so they should be kept. > > Is anyone doing so though? Not that I've seen. > I recall proposing a couple months ago that we kill those makefiles, > but there was at least one objection at the time. > > It occurs to me that the availability of the native port > might actually > increase rather than decrease the demand for these makefiles --- or at > least the demand for the ability to build libpq that way. Consider > people who are building database-using apps using MSVC or Borland. They don't need to build libpq themselves though - we provide import libs with the installer for VC++ that allows the supplied mingw build of the dll to be used (that's how pgAdmin is built). I'm sure that a Borland lib could be generated in the same way if anyone had the equivalent Borland tool (with VC++ we use lib.exe). My main concern is that they don't end up suffering terminal bit-rot because I stop helping maintain them - if we ship them, they should work. Regards, Dave.
В списке pgsql-patches по дате отправления: