On Fri, Jul 27, 2007 at 10:01:06PM +0200, Magnus Hagander wrote: > Hiroshi Saito wrote: > >>>> Ok. So there are actually two ways to go about it: > >>>> 1) Discontinue support for MSVC6 and require MSVC8 > >>>> > >>>> 2) Change it so that MSVC6 can still build libpq, just not with SSPI > >>>> support. This can be done by conditionally enabling ENABLE_SSPI, so > >>>> it's > >>>> not that hard. > >>>> > >>>> The question is, if we go with option 2, is it something that anybody > >>>> actually will *use*? > >>> > >>> I desire 1 as formal. However, It contains VC7.1 and VC8. > >>> Moreover, libpq.dll can be used by the module of VC6. > >> > >> Is there any actual reason to keep VC7.1 support? > > > > It is still used and has sufficient function. Then, Inoue-san is > > developing in the environment.:-) > > The project file of VC7.1 differs from VC8 a little. However, nmake.exe > > absorbs it. > > for the reasons, we are maintaining win32.mak. but, project file offers > > the minimum function > > in simple. MSDTC is a reason for being somewhat more complicated than > > standard compile. > > Ok. Just to be clear, do you need MSVC7.1 support, or do you need > win32.mak/nmake support? I realize they both work here, but if we > changed something else that needed MSVC8 but maintained the win32.mak > file, would that be enough?
Since I've had no further feedback, I've applied a patch that changes the list of supported MSVC versions to 7.1-8.0, but keeping the win32.mak files. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
