pajoye Wed Jul 2 20:53:36 2008 UTC
Modified files:
/php-src/win32/buildbuildconf.js
Log:
- MFB: improve ADD_EXTENSION_DEP detection
http://cvs.php.net/viewvc.cgi/php-src/win32/build/buildconf.js?r1=1.17r2=1.18diff_format=u
Index:
mattwil Wed May 14 11:32:28 2008 UTC
Modified files:
/php-src/win32/buildbuildconf.js
Log:
MFB: The Steph special :-) to allow plain 'configure' to be used
http://cvs.php.net/viewvc.cgi/php-src/win32/build/buildconf.js?r1=1.16r2=1.17diff_format=u
Index:
edink Sat Sep 17 18:07:22 2005 EDT
Modified files:
/php-src/win32/buildbuildconf.js
Log:
MFB
http://cvs.php.net/diff.php/php-src/win32/build/buildconf.js?r1=1.13r2=1.14ty=u
Index: php-src/win32/build/buildconf.js
diff -u
wez Mon Aug 2 21:23:35 2004 EDT
Modified files:
/php-src/win32/buildbuildconf.js
Log:
Catch exceptions from broken config.w32 files
http://cvs.php.net/diff.php/php-src/win32/build/buildconf.js?r1=1.11r2=1.12ty=u
Index:
I think what both of you are saying is true, both that it's much easier to
maintain the build parameters and to build a custom version. However, for
the actual coding and debugging you still need the VC++ environment and
browse database and the ability to set the breakpoint in the source. I
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/buildbuildconf.js config.w32
Log:
Fix bug #26692; Could not find GetLongPathNameA
Does this mean we can't be binary compatible with NT4?
Andi
At 03:01 PM 12/22/2003 +, 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
Message -
From: Andi Gutmans [EMAIL PROTECTED]
To: Wez Furlong [EMAIL PROTECTED]; [EMAIL PROTECTED]
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
-CVS] cvs: php-src /win32/build buildconf.js config.w32
TSRM config.w32 tsrm_win32.c tsrm_win32.h
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
At 07:20 PM 12/22/2003 +, Wez Furlong wrote:
No additional DLL's are needed. We can keep the news
entry about dropping win95 support I think, even if
the binaries still work there; it is nice to say good
riddance to it (we might end up using some other API
that isn't supported under win95 in
I don't really mind how the snapshots are built but it is crucial for
Windows development to keep the .dsp's working and up-to-date. It's the
only sane way to develop debug on Windows.
You can still use the VC++ or VS.Net IDE to debug and write code using
the new build system.
One of the
Hi,
I would like to back this up. With the .dsp files there is too many
hardcoded parameters that you need to make sure is up to date, and it
requires headers and libraries to be in specific places. With the new
build system you can organize your files almost as you wish and it is much
easier to
-CVS] cvs: php-src /win32/build buildconf.js config.w32
TSRM config.w32 tsrm_win32.c tsrm_win32.h
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
wez Mon Dec 22 20:54:07 2003 EDT
Modified files:
/php-src/win32/buildbuildconf.js
Log:
win32 buildconf now honours extension dependencies and will
try its best to ensure that the config.w32 files are amalgamated
in such a way that modules are
wez Wed Dec 3 20:59:46 2003 EDT
Modified files:
/php-src/win32/buildbuildconf.js
Log:
be safe...
Index: php-src/win32/build/buildconf.js
diff -u php-src/win32/build/buildconf.js:1.3 php-src/win32/build/buildconf.js:1.4
---
15 matches
Mail list logo
