Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37593 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83880 invoked from network); 11 May 2008 13:15:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2008 13:15:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=hsantos@isdg.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=hsantos@isdg.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain isdg.net designates 208.247.131.9 as permitted sender) X-PHP-List-Original-Sender: hsantos@isdg.net X-Host-Fingerprint: 208.247.131.9 ntbbs.winserver.com Windows NT 4.0 (older) Received: from [208.247.131.9] ([208.247.131.9:4497] helo=winserver.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/3F-34108-F71F6284 for ; Sun, 11 May 2008 09:15:44 -0400 Received: from mail.winserver.com ([208.247.131.9]) by winserver.com (Wildcat! SMTP Router v6.3.452.5) for internals@lists.php.net; Sun, 11 May 2008 09:14:26 -0400 Received: from hdev1 ([72.144.198.133]) by winserver.com (Wildcat! SMTP v6.3.452.5) with ESMTP id 953012203; Sun, 11 May 2008 09:14:25 -0400 Message-ID: <4826F147.1030609@isdg.net> Date: Sun, 11 May 2008 09:14:47 -0400 Organization: Santronics Software, Inc. User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Pierre Joye CC: internals@lists.php.net References: <4826958F.7010900@isdg.net> <4826ABFC.6080104@isdg.net> <4826C3F6.1020507@isdg.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] README.WIN32-BUILD-SYSTEM From: hsantos@isdg.net (Hector Santos) Pierre Joye wrote: >> Ok, then may I suggest the *.DSP/DSW project files in the PHP5+ >> distribution either a) removed from the distribution, or b) updated. > > Removing them sounds like the best option yes. I hope not. :-) > 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. :-) > 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. > 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.) > 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: 2006-09-07 Rob Richards * (PHP_5_2) ext/libxml/php_libxml2.def: MFH: fix def file for 2.6.26 (xmlXPathCompiledEvalToBoolean required in .27) * ext/libxml/php_libxml2.def: fix def file for 2.6.26 (xmlXPathCompiledEvalToBoolean required in .27) >> 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/ -- Hector Santos