I don't want to burst your bubble, but PHP 5 is the current release of PHP, and we've started work on PHP 6. The win32 build system is much more friendly; I've already spent many hours on making things better there.
If you want to improve things for PHP 4, go for it, but I don't and won't have time to help review it; my "php time" is focused on the current stuff. Don't forget that we have full-on win32 builds being generated courtesy of Edin, along with several snapshot builds throughout the day for all branches of PHP and PECL; there should be very little need for people to build their own, unless they are hacking on PHP itself--those people should be maintaining their own build environments. --Wez. On 10/22/05, techtonik <[EMAIL PROTECTED]> wrote: > > If you have cygwin flex and bison, you don't need to copy anything. > > And if I don't have any? Can it be made as simple as "unpack and compile"? > If you'll read this page > http://www.php.net/manual/en/install.windows.building.php > you notice redundant instructions for copying files and setting up > MSVC++. I've made a .bat file to automate the process and avoid making > these repeated operations manually every time I need to compile PHP 4 > for testing. I'm looking into get this process even more simple and > without unnecessary garbage left on my c: drive. Files are attached. > > > You also don't *have* to recompile resolv.lib; just build a release > > build and use that, even when you're building a debug version of PHP. > > Why do I need to build it at all if it is included in win32build.zip? > > Should I update installation instructions on > http://www.php.net/manual/en/install.windows.building.php then? > > > > > --Wez. > > > > On 10/22/05, techtonik <[EMAIL PROTECTED]> wrote: > > > ||*()*|| Greetings, phpinnards.. =) > > > > > > I tried to automate build system for PHP 4 a bit and after that > > > can't get some stupid questions out of my head. Install instructions > > > located as usual > > http://www.php.net/manual/en/install.windows.building.php > > > > > > There are at least two inconveniences: > > > 1. Need to copy bison.sample from win32build\bin to c:\usr\local\lib > > > 2. Need to recompile resolv.lib every time target changes > > > > > > So the questions are the following > > > 1.1 Why not to get rid of this bison.sample copy operation either by > > > 1.1.1 upgrade bison.exe in win32build.zip from 1.27 to at > > > least 1.34, which adds -S options to specify bison.sample > > > explicitly and also includes some memory leak fixes > > > > > http://sourceforge.net/project/shownotes.php?release_id=274058 > > > or > > > 1.1.2 set up environment variable BISON_SIMPLE somewhere in > > > build files/scripts? > > > > > > 2.1 Why resolv.lib needs to be recompiled every time when target > > > changes from "debug" to "release" and vice versa > > > 2.1.1 Why it is not possible to supply a separate resolv_debug.lib > > > and resolv_release.lib files in win32build.zip and rewrite > > > dependencies for them in windows build files? > > > > > > Thanks. > > > > > > .techtonik > > > -- > > > > > > -- > > > PHP Internals - PHP Runtime Development Mailing List > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
