libxml2

Libxml is a XML processor written by Daniel Veillard for the GNOME project... yea, that is the official statement, but he wrote it for fun, whatever he says :-). It implements a whole lot of existing standards related to markup languages and a few extras as well. Used together with its close friends libxslt, xmlsec and gdome, it forms a full-featured general-purpose toolkit for XML. Although sometimes referred to as GNOME-XML, libxml does not depend on GNOME but rather the other way around. This place is devoted to accomodating libxml to the oddities of the Windows operating system and provides the last-known-good binaries for the native Windows platform. The source code is not hosted on this site. Pay a visit to the libxml official home for that. The binaries are available in the download area. However, read this document in its entirety before you grab any of these. First check what you need to download. There are several packages available and some of them depend on the others. The packages available on this site are: libxml2, the XML parser and processor. libxslt, the XSL and EXSL Transformations processor. xmlsec, the XMLSec and XMLDSig processor. xsldbg, the XSL Transformations debugger. openssl, the general crypto toolkit. iconv, the character encoding toolkit. zlib, the compression toolkit. To satisfy the dependencies, look up the desired package and get that and everything else below, following the arrows. The blue arrows show the mandatory dependencies, you'll never get through without these. The gray arrows represent the dependencies which can be removed through recompiling. For the binary packages to work, you must follow all arrows. If you wish to use libxml solely through the supplied utilities, such as xmllint or xsltproc, then all you need to do is place the contents of the bin directory from the binary package in a directory on your disc which is mentioned in your PATH environment variable. You can use an existing directory which is allready in the path, such as C: WINDOWS. You can also create a new directory for libxml and place the files there, but be sure to modify the PATH environment variable and add that new directory to its list. If you use other software which needs libxml, such as Apache Web Server in certain configurations (PHP, for example), then please consult the documentation of that software and see if it mentions something about how it uses libxml and how it expects it to be installed. If you find nothing, then the default installation, as described in the previous paragraph, should be suficient. All binaries which you can download from this site use the multithreaded dynamic C-runtime (msvcrt.dll). Every program you compile using these binaries must use the same runtime. Unless you like your app crashing, set up your project to use msvcrt.dll. If you for some reason must use a different runtime, then you must get the source and compile libxml and friends yourself. If you link to libxml statically, make sure that @lib@ STATIC macro is defined during the compilation of your sources, where @lib@ stands for LIBXML, LIBXSLT, LIBEXSLT and XMLSEC respectively. As of verson 2.5.7, libxml binary is being distributed with thread-suport enabled. This means that this version is not binary compatible to the previous versions. If you currently use an older version of any package from this site, you will have to upgrade all packages which have 'xml' or 'xsl' in their name. All binaries have been built using C/C++ compiler version 13, linker version 7 and nmake version 6, all of them by Microsoft Corporation. To avoid any confusion, these are not the tools you get when you install Microsoft Visual Studio. These are a part of the Windows XP DDK. If you have other development tools, such as Borland's, check if you can use these binaries as they are before building your own. You should be able to. There is a lot of documentation about this software, as well as there is argue about its completeness a