NSAPI snaps build

Hi Pierre,

> > > 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).

I installed a recent version of SJSWS on my local box now and wanted to
download the 5.3 snapshots. The VC6 snapshot contains NSAPI in both the TS
and NTS version. On the other hand, the VC9 version does not contain NSAPI.
The configure log shows, that nsapi.h was not found. There is something
weird. Correct should be:

- VC6 TS: nsapi enabled and .h/.lib files available
- VC6 NTS: nsapi disabled or .h/.lib files removed
- VC9 TS: nsapi enabled and .h/.lib files available
- VC9 NTS: nsapi disabled or .h/.lib files removed

Can you correct this and build some new snapshots?

I will then test tomorrow, as soon as there is again a new VC9 snapshot.

FYI: The latest SJSWS 7.0U4 is still linked against VC6, but according to my
previous mails, it should work because VC6 and VC9 CRTs can coexist as long
as no resources are shared between both CRTs. NSAPI has a private API, the
only shared structs between VC6 and VC9 would be: "struct stat", which is
hopefully identical. All other resources used as parameters to functions are
simple handles or private structs. No malloc or other CRT resources are
shared/used.

Uwe