Update README

This commit is contained in:
Nick Wellnhofer 2024-10-31 17:38:37 +01:00
parent 467f444544
commit 36117723d4

View File

@ -66,7 +66,6 @@ The following options disable or enable code modules and relevant symbols:
--with-schematron Schematron support (on)
--with-threads multithreading support (on)
--with-thread-alloc per-thread malloc hooks (off)
--with-tree DOM like tree manipulation APIs (on)
--with-valid DTD validation support (on)
--with-writer xmlWriter serialization interface (on)
--with-xinclude XInclude 1.0 support (on)
@ -121,6 +120,9 @@ directly in various IDEs such as CLion, QtCreator, or Visual Studio.
### Meson
Still somewhat experimental, see
[issue 743](https://gitlab.gnome.org/GNOME/libxml2/-/issues/743).
Libxml can also be built with meson. Without option, simply call
meson setup builddir
@ -146,24 +148,24 @@ To launch tests:
## Dependencies
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).
libxml2 supports POSIX and Windows operating systems.
The iconv function is required for conversion of character encodings.
This function is part of POSIX.1-2001. If your platform doesn't provide
iconv, you need an external libiconv library, for example
[GNU libiconv](https://www.gnu.org/software/libiconv/). Alternatively,
you can use [ICU](https://icu.unicode.org/).
[GNU libiconv](https://www.gnu.org/software/libiconv/). Using
[ICU](https://icu.unicode.org/) is also supported but discouraged.
If enabled, libxml uses [libz](https://zlib.net/) or
[liblzma](https://tukaani.org/xz/) to support reading compressed files.
Use of this feature is discouraged.
The xmllint executable uses libreadline and libhistory if enabled.
## Contributing
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
The current version of the code can be found in GNOME's GitLab at
<https://gitlab.gnome.org/GNOME/libxml2>. The best way to get involved
is by creating issues and merge requests on GitLab.
All code must conform to C89 and pass the GitLab CI tests. Add regression