RE: [INTERNALS-WIN] RE: [PHP-DEV] Differences in VC6 and VC9 Windows builds and MSSQL Driver.

> > I am not sure, if VC6 can be dropped easily. E.g. some SAPIs that
> directly
> > map into servers may have problems if using the wrong CRT. Until now, I
> had
> > no time to build up a Windows "Sun Java System Webserver" and test it
> with
> > both CRTs. The code compiles fine on the snaps box, but I am not sure,
> if
> > the DLL loads into the server.
> 
> VC6 will be droped after 5.3.0. VC6 can't be supported anymore, it is
> already a real pain to maintain as most of the modern tools or APIs do
> not work with it, the licenses can't be built anymore, etc.

I think we should do some announcement to the SAPI maintainers to ask them
to check their modules with their servers (if the SAPI is available for
Windows). For NSAPI, I will do this some time in future (low priority),
because it is some work to install a windows server and add SJSWS 7.0 to it
and possibly debug it (if it does not work). SJSWS is not able to run on my
local Win XP Prof (I am not sure about this, maybe it works, I will give it
a try).

> > To the snaps build: The NSAPI module tests for "#define ZTS" and does
> > therefore not compile without thread safety. Why do the windows non-ts
> > builds on snaps.php compile? Is ZTS on windows always defined (it looks
> like
> > so in the makefile). How to test on windows, if thread safety is
> available?
> > But better would be to disable thread-unsafe builds for the NSAPI SAPI
> from
> > the beginning.
> 
> 
> NSAPI is disabled for the NTS builds. They were not explicitly
> disabled after I reinstalled the snaps box :).

Thanks, I have not checked this the last days (since release of 5.2.8).

Uwe