Re: cvs: php-src /win32/build buildconf.js config.w32 TSRM config.w32 tsrm_win32.c tsrm_win32.h

From: Date: Mon, 22 Dec 2003 18:49:41 +0000
Subject: Re: cvs: php-src /win32/build buildconf.js config.w32 TSRM config.w32 tsrm_win32.c tsrm_win32.h
References: 1  Groups: php.cvs 
Request: Send a blank email to php-cvs+get-25383@lists.php.net to get a copy of this message
The main question is how will the PHP builds be created from now on? With this SDK? Will we have to include additional dlls with the distro? Am I supposed to nuke the NEWS entry about not supporting Win95? Andi At 05:55 PM 12/22/2003 +0000, Wez Furlong wrote:
We can if we are building against the platform SDK headers; the NewAPIs.h file defines some smart stubs that will use GetProcAddress to determine if the system really has the API, but will fall back on emulation if it is not present. If we don't use that header file, then we can not run under win95 or NT4. --Wez. ----- Original Message ----- From: "Andi Gutmans" <andi@zend.com> To: "Wez Furlong" <wez@php.net>; <php-cvs@lists.php.net> Sent: Monday, December 22, 2003 4:39 PM Subject: Re: [PHP-CVS] cvs: php-src /win32/build buildconf.js config.w32 TSRM config.w32 tsrm_win32.c tsrm_win32.h Does this mean we can't be binary compatible with NT4? Andi At 03:01 PM 12/22/2003 +0000, Wez Furlong wrote:
wez             Mon Dec 22 10:01:06 2003 EDT
Added files:
    /TSRM       config.w32
Modified files:
    /TSRM       tsrm_win32.c tsrm_win32.h
    /php-src/win32/build        buildconf.js config.w32
Log: Fix bug #26692; Could not find GetLongPathNameA under NT4. This fix relies on you having the Platform SDK headers. Using the new build system, the NewAPIs.h header will be detected automatically, however, for people building using .dsp files, you will need to add /DHAVE_NEWAPIS_H=1 to the TSRM project if you have those newer headers.


« previous php.cvs (#25383) next »