Skip to content

Commit df72c31

Browse files
committed
Change the ABI to libxml++-4.0 instead of libxml++-3.0.
This installs in parallel with libxml++-3.0.
1 parent 18b9537 commit df72c31

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

configure.ac

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ AM_MAINTAINER_MODE([disable])
1818
AC_ARG_VAR([ACLOCAL_FLAGS], [aclocal flags, e.g. -I <macro dir>])
1919

2020
MM_PREREQ([0.9.10])
21-
MM_INIT_MODULE([libxml++-3.0])
21+
MM_INIT_MODULE([libxml++-4.0])
2222

2323
# Tell mm-common-prepare to copy the mm-common .pl scripts
2424
# and some other files into docs/, and use them from there,

docs/manual/libxml++_without_code.xml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ url="http://www.gnome.org">GNOME</ulink> project, of which libxml++ is a part.</
4747
# apt-get install libxml++3.0-dev libxml++3.0-doc
4848
</programlisting>
4949
</para>
50-
<para>To check that you have the libxml++ development packages installed, and that your environment is working properly, try <command>pkg-config libxml++-3.0 --modversion</command>.</para>
50+
<para>To check that you have the libxml++ development packages installed, and that your environment is working properly, try <command>pkg-config libxml++-4.0 --modversion</command>.</para>
5151
<para>Links for downloading and more documentation can be found at <ulink
5252
url="http://libxmlplusplus.sourceforge.net">libxmlplusplus.sourceforge.net</ulink>.
5353
libxml++ is licensed under the LGPL, which allows its use via dynamic linking in both open source and closed-source software. The underlying libxml2 library uses the even more generous MIT licence.</para>
@@ -64,11 +64,11 @@ url="http://libxmlplusplus.sourceforge.net">libxmlplusplus.sourceforge.net</ulin
6464
<sect1>
6565
<title>Compilation and Linking</title>
6666
<para>To use libxml++ in your application, you must tell the compiler where to find the include headers and where to find the libxml++ library. libxml++ provides a pkg-config .pc file to make this easy. For instance, the following command will provide the necessary compiler options:
67-
<command>pkg-config libxml++-3.0 --cflags --libs</command>
67+
<command>pkg-config libxml++-4.0 --cflags --libs</command>
6868
</para>
6969
<para>When using autoconf and automake, this is even easier with the PKG_CHECK_MODULES macro in your configure.ac file. For instance:
7070
<programlisting>
71-
PKG_CHECK_MODULES(SOMEAPP, libxml++-3.0 >= 3.0.0)
71+
PKG_CHECK_MODULES(SOMEAPP, libxml++-4.0 >= 4.0.0)
7272
AC_SUBST(SOMEAPP_CFLAGS)
7373
AC_SUBST(SOMEAPP_LIBS)
7474
</programlisting>

libxml++/libxml++.h

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,14 +33,14 @@
3333
*
3434
* If your source file is @c program.cc, you can compile it with:
3535
* @code
36-
* g++ program.cc -o program `pkg-config --cflags --libs libxml++-3.0`
36+
* g++ program.cc -o program `pkg-config --cflags --libs libxml++-4.0`
3737
* @endcode
3838
* If your version of g++ is not C++11-compliant be default,
3939
* add the @c -std=c++11 or @c -std=c++0x option.
4040
*
4141
* Alternatively, if using autoconf, use the following in @c configure.ac:
4242
* @code
43-
* PKG_CHECK_MODULES([LIBXMLXX], [libxml++-3.0])
43+
* PKG_CHECK_MODULES([LIBXMLXX], [libxml++-4.0])
4444
* @endcode
4545
* Then use the generated @c LIBXMLXX_CFLAGS and @c LIBXMLXX_LIBS variables in
4646
* the project @c Makefile.am files. For example:

0 commit comments

Comments
 (0)