Hi Hector, On Sun, May 11, 2008 at 3:14 PM, Hector Santos <[EMAIL PROTECTED]> wrote:
> > It is not really subjective, it is based on our experiences and > > feedbacks from other users. > > It still subjective. :-) Besides, I would venture the negative experiences > were based on the fact they never updated so people were having "headache > causing" issues. Based on what I seen so far, compiling via current method > is like pulling teeth. :-) What is hard in: 1. mkdir c:\phpw32 2. extract a php release in c:\phpw32\php-5.y.z 3. extract the dependencies in c:\phpw32\php_builds 4. run: buildconf.bat configure.bat [option your like to have} nmake > > It is already enough work to keep everything up and running. > > Sure, so the more automation "out the box" the better. Anyway, IMV, you > will never let go the need to support smart frontends. Smart? We do not support them whether they are smart or not is not the point ;) > > Project files have no benefit over the current script. > > Well, I don't see why not. You can do the same thing via project files - > see the "Custom Build", "Pre-Link", "Post-Build" tabs. In fact, I am going > to prove it when I can the chance. (BTW, I program almost exclusively under > a console, so its not "windows-users" thing.) My point is to focus on what we actually need or work on. I will not try to stop you on your attempt to fix the VC project files but it is not what we need. If you like to help us in the windows build process then there is numerous ways to do it: - help us to document the process - help us to build more dependencies as well porting some of them to Windows (and Visual c++ 6/2005/2008) - test our builds The other reasons why projects file are useless for us is their static nature. Unless we write a sln generator, it makes little sense to use them when you work with php, PECL and your own extensions. And that's we do for the PHP releases and our developments. > > If you like to write a howto for beginners out of your experiences, > > you will be more than welcome :-) > > I have started this and my first test of instructions and new batch files > was perfect for php 5.2.5, however re-running it for PHP 5.2.6 errored out > on an unresolved link for: > > xmlXPathCompiledEvalToBoolean > > Removing this from the release_ts\php5ts.dll.def allowed it to successfully > link. > > I have not deeply stupid why yet, but I did noticed in the Changelog > comments related to this function: Have you read the wiki? :) Please fetch the libxml we use for 5.2.6 here: http://pecl2.php.net/downloads/php-windows-builds/php-libs/ (use the right version with your compiler) > >> I don't understand why the CVS bundle folder has this as > >> dead files, if they are still required for a build. > > > > Which CVS bundle folder? > > http://cvs.php.net/viewvc.cgi/php-src/ That's the main PHP CVS module. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
