libxml++ for Mac

libxml++ C++ interface to libxml2 and XML files.

Introduction

libxml++ (a.k.a. libxmlplusplus) provides a C++ interface to XML files. It uses libxml2 to access the XML files, and in order to configure libxml++ you must have both libxml2 and pkg-config installed.

libxml++-2.6, libxml++-3.0, libxml++-4.0 and libxml++-5.0 are different parallel-installable ABIs. This file describes libxml++-5.0.

See the examples directory for example code.

Use pkg-config to discover the necessary include and linker arguments. For instance,

If you build with Autotools, ideally you would use PKG_CHECK_MODULES in your configure.ac file.

General information

Web site https://libxmlplusplus.github.io/libxmlplusplus/

Download location https://download.gnome.org/sources/libxml++/ (until 5.4.0) https://github.com/libxmlplusplus/libxmlplusplus/releases/

Reference documentation https://libxmlplusplus.github.io/libxmlplusplus/reference/html/

Tarballs contain reference documentation. In tarballs generated with Meson, see the untracked/docs/reference/html directory.

Discussion on GNOME's discourse forum https://discourse.gnome.org/tag/cplusplus https://discourse.gnome.org/c/platform

Git repository https://github.com/libxmlplusplus/libxmlplusplus

Bugs can be reported to https://github.com/libxmlplusplus/libxmlplusplus/issues

Patches can be submitted to https://github.com/libxmlplusplus/libxmlplusplus/pulls

Building

Whenever possible, you should use the official binary packages approved by the supplier of your operating system, such as your Linux distribution.

Building the documentation

The reference documentaion is built with Doxygen.

The manual is a DocBook 5.0 document. These packages are recommended when building the manual (can have other names in other distros): docbook5-xml (Ubuntu and Debian) or docbook5-schemas (Fedora) docbook-xsl (Ubuntu and Debian) or docbook-style-xsl (Fedora)

It may be possible to build without these packages, but it will be slow and error prone. The xmllint command is told to read files from http://docbook.org. The xsltproc command is told to read files from http://docbook.sourceforge.net. The commands first search for local copies of those files. If local copies exist and are installed at expected locations, the commands make no network accesses.

Building on Windows

See MSVC-Builds

Building from a release tarball

Extract the tarball and go to the extracted directory:

It's easiest to build with Meson, if the tarball was made with Meson, and to build with Autotools, if the tarball was made with Autotools. Then you don't have to use maintainer-mode.

How do you know how the tarball was made? If it was made with Meson, it contains files in untracked/docs/ and other subdirectories of untracked/.

Building from a tarball with Meson

Don't call the builddir 'build'. There is a directory called 'build' with files used by Autotools.

If the tarball was made with Autotools, you must enable maintainer-mode: