libxml++ alternatives and similar libraries
Based on the "XML" category.
Alternatively, view Libxml2 alternatives based on common mentions on social networks and blogs.
TinyXML8.6 0.0 L1 libxml++ VS TinyXMLTinyXML2 is a simple, small, efficient, C++ XML parser that can be easily integrated into other programs.
PugiXML7.9 3.9 L1 libxml++ VS PugiXMLLight-weight, simple and fast XML parser for C++ with XPath support
Libxml25.2 9.6 L2 libxml++ VS Libxml2Read-only mirror of https://gitlab.gnome.org/GNOME/libxml2
Xerces-C++2.9 0.0 L1 libxml++ VS Xerces-C++Apache Xerces-C validating XML parser
TinyXML++2.7 0.0 L2 libxml++ VS TinyXML++Completely new interface to TinyXML
Expat1.5 0.0 L3 libxml++ VS ExpatThe Expat XML Parser
RapidXmlAn attempt to create the fastest XML parser possible, while retaining useability, portability and reasonable W3C compatibility. [Boost]
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of libxml++ or a related project?
libxml2 is an XML toolkit implemented in C, originally developed for the GNOME Project.
Full documentation is available at https://gitlab.gnome.org/GNOME/libxml2/-/wikis.
Bugs should be reported at https://gitlab.gnome.org/GNOME/libxml2/-/issues.
A mailing list [email protected] is available. You can subscribe at https://mail.gnome.org/mailman/listinfo/xml. The list archive is at https://mail.gnome.org/archives/xml/.
This code is released under the MIT License, see the Copyright file.
libxml2 can be built with GNU Autotools, CMake, or several other build systems in platform-specific subdirectories.
Autotools (for POSIX systems like Linux, BSD, macOS)
If you build from a Git tree, you have to install Autotools and start by generating the configuration files with:
If you build from a source tarball, extract the archive with:
tar xf libxml2-xxx.tar.gz cd libxml2-xxx
To see a list of build options:
Also see the INSTALL file for additional instructions. Then you can configure and build the library:
./configure [possible options] make
Note that by default, no optimization options are used. You have to enable them manually, for example with:
CFLAGS='-O2 -fno-semantic-interposition' ./configure
Now you can run the test suite with:
Please report test failures to the mailing list or bug tracker.
Then you can install the library:
At that point you may have to rerun ldconfig or a similar utility to update your list of installed shared libs.
CMake (mainly for Windows)
Another option for compiling libxml is using CMake:
cmake -E tar xf libxml2-xxx.tar.gz cmake -S libxml2-xxx -B libxml2-xxx-build [possible options] cmake --build libxml2-xxx-build cmake --install libxml2-xxx-build
Common CMake options include:
-D BUILD_SHARED_LIBS=OFF # build static libraries -D CMAKE_BUILD_TYPE=Release # specify build type -D CMAKE_INSTALL_PREFIX=/usr/local # specify the install path -D LIBXML2_WITH_ICONV=OFF # disable iconv -D LIBXML2_WITH_LZMA=OFF # disable liblzma -D LIBXML2_WITH_PYTHON=OFF # disable Python -D LIBXML2_WITH_ZLIB=OFF # disable libz
You can also open the libxml source directory with its CMakeLists.txt directly in various IDEs such as CLion, QtCreator, or Visual Studio.
Libxml does not require any other libraries. A platform with somewhat recent POSIX support should be sufficient (please report any violation to this rule you may find).
However, if found at configuration time, libxml will detect and use the following libraries:
- libz, a highly portable and widely available compression library.
- liblzma, another compression library.
- libiconv, a character encoding conversion library. The iconv function is part of POSIX.1-2001, so libiconv isn't required on modern UNIX-like systems like Linux, BSD or macOS.
- ICU, a Unicode library. Mainly useful as an alternative to iconv on Windows. Unnecessary on most other systems.
The current version of the code can be found in GNOME's GitLab at at https://gitlab.gnome.org/GNOME/libxml2. The best way to get involved is by creating issues and merge requests on GitLab. Alternatively, you can start discussions and send patches to the mailing list. If you want to work with patches, please format them with git-format-patch and use plain text attachments.
All code must conform to C89 and pass the GitLab CI tests. Add regression tests if possible.
- Daniel Veillard
- Bjorn Reese
- William Brack
- Igor Zlatkovic for the Windows port
- Aleksey Sanin
- Nick Wellnhofer
*Note that all licence references and agreements mentioned in the libxml++ README section above are relevant to that project's source code only.