Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25644 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38484 invoked by uid 1010); 13 Sep 2006 01:41:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38469 invoked from network); 13 Sep 2006 01:41:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Sep 2006 01:41:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=rrichards@ctindustries.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rrichards@ctindustries.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ctindustries.net from 216.117.147.250 cause and error) X-PHP-List-Original-Sender: rrichards@ctindustries.net X-Host-Fingerprint: 216.117.147.250 unknown Linux 2.4/2.6 Received: from [216.117.147.250] ([216.117.147.250:45754] helo=ctindustries.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 05/B1-02095-EA167054 for ; Tue, 12 Sep 2006 21:41:03 -0400 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) (authenticated bits=0) by ctindustries.net (8.12.8/8.12.8) with ESMTP id k8D1c4M0020448; Tue, 12 Sep 2006 21:38:11 -0400 Message-ID: <450761A6.5030004@ctindustries.net> Date: Tue, 12 Sep 2006 21:40:54 -0400 User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 To: Stanislav Malyshev CC: "'PHP Internals'" References: <45072B31.2070301@zend.com> <4507580B.70301@ctindustries.net> <45075BD4.4040508@zend.com> In-Reply-To: <45075BD4.4040508@zend.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/1864/Tue Sep 12 04:54:22 2006 on ctindustries.net X-Virus-Status: Clean Subject: Re: [PHP-DEV] libxml2 build for php 5.2 on windows From: rrichards@ctindustries.net (Rob Richards) Stanislav Malyshev wrote: > Hi! > Thanks for the quick answer! > >> 2.6.26 built using the LIBXML_STATIC_FOR_DLL flag. >> > Ehm, ok. The problem is that it is not possible to define this flag in > any way but by hand-editing makefile. Which reinforces my point about > keeping working one in win32build zip. > Right. I have a patch that I asked some of the people who distribute windows builds of libxml2 to take a look at so that the lib gets built by default. > >> It should be using the static version included from: >> http://ctindustries.net/libxml/. The library was not renamed as to >> minimize the change. >> > This URL does not seem to be alive, anyway - what is this URL? It's not > standard libxml2 place - where one finds it out (except for asking on > the list each time one want to build PHP ;) > It should be as i just checked it. It contains the builds I have been maintaining for the past few years now and the ones Edin uses for the windows builds. The libxslt build there has been required from day one cause it a customized build. It's just recent that the libxml2 build is now non-standard as well. At that URL you should find both release and debug builds of libxml2 and libxslt specifically for building with PHP. >> I am working on getting this lib built by default within the standard >> release. At that time, I will change the required lib as I have >> proposed to name it libxml2_a_dll.lib. >> > Please do not forget to update .dsp files then. > >> This would require the win32build package to be versioned so that the >> correct version of libxml2 is used (needs to support the symbols being >> exported from the .def file). >> > Does it mean older PHP versions won't build with newer libxml? Ouch. > Then I guess we need versioned files. Because right now building 5.2 on > windows is very non-obvious to say the least and there's no reason why > it should stay that way. Anyway, since older version did not have libxml > at all, I think it won't be too bad adding one, > Older versions will still build with the standard libxml2 builds, just not the ones I provide. They will compile, but the thread cleanup handling will be a bit pooched. Best I could do if this is absolutely necessary is to build and provide all 3 libs and change the code on the recent branches (we've change 6, 5.2 and domxml in 4.4) to use libxml2_a_dll.lib (my proposed name for the new library). Rob