Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3460
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <01d101c34c7e$3a628030$06dea8c0@cyberware.local>
To: <internals@lists.php.net>
Date: Thu, 17 Jul 2003 12:12:31 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: libxml windows binaries: if anyone cares
From: rrichards@ctindustries.net ("Rob Richards")

Whomever said that there are no issues with libxml as the api doesnt change,
sure didnt take into account that the functionality does change which can
really break things until it its well tested and fixed (both 2.5.7 and 2.5.8
binaries have issues affecting php5). The binaries from the libxml windows
maintainer are occasionally updated with the latest code, so hopefully the
next 2.5.8 will be rolled within the next few weeks.

This also means that some versions of 2.5.8 from non windows distros will
most likely cause the same problems, all depending upon when it was built
and what release of the package.

If anyone needs a working libxml binary for windows , I packaged a debug and
release version (FOR DEVELOPMENT PURPOSES ONLY). You can grab them from:

http://www.ctindustries.net/dom/libxml2-2.5.8.phpdebug.zip
http://www.ctindustries.net/dom/libxml2-2.5.8.php.zip

The release version is completely untested.
The debug version, which I am using, is a debug build with libxml memory
debugging enabled.

They are both built from the stock 2.5.8 tar.gz file with only the code
which is breaking under php5 patched (the changes are now in libxml cvs as
well).

Rob