[libxml++] Change the ABI to libxml++-4.0 instead of libxml++-3.0.



commit df72c313ed1e610c2b891a3e8dcbf2b469db70a7
Author: Murray Cumming <murrayc murrayc com>
Date:   Mon Nov 14 11:09:18 2016 +0100

    Change the ABI to libxml++-4.0 instead of libxml++-3.0.
    
    This installs in parallel with libxml++-3.0.

 configure.ac                          |    2 +-
 docs/manual/libxml++_without_code.xml |    6 +++---
 libxml++/libxml++.h                   |    4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/configure.ac b/configure.ac
index 998ad18..1686cdb 100644
--- a/configure.ac
+++ b/configure.ac
@@ -18,7 +18,7 @@ AM_MAINTAINER_MODE([disable])
 AC_ARG_VAR([ACLOCAL_FLAGS], [aclocal flags, e.g. -I <macro dir>])
 
 MM_PREREQ([0.9.10])
-MM_INIT_MODULE([libxml++-3.0])
+MM_INIT_MODULE([libxml++-4.0])
 
 # Tell mm-common-prepare to copy the mm-common .pl scripts
 # and some other files into docs/, and use them from there,
diff --git a/docs/manual/libxml++_without_code.xml b/docs/manual/libxml++_without_code.xml
index 1648f9f..9158d11 100644
--- a/docs/manual/libxml++_without_code.xml
+++ b/docs/manual/libxml++_without_code.xml
@@ -47,7 +47,7 @@ url="http://www.gnome.org";>GNOME</ulink> project, of which libxml++ is a part.</
     # apt-get install libxml++3.0-dev libxml++3.0-doc
     </programlisting>
     </para>
-    <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>
+    <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>
     <para>Links for downloading and more documentation can be found at <ulink
 url="http://libxmlplusplus.sourceforge.net";>libxmlplusplus.sourceforge.net</ulink>.
     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
     <sect1>
     <title>Compilation and Linking</title>
     <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:
-    <command>pkg-config libxml++-3.0 --cflags --libs</command>
+    <command>pkg-config libxml++-4.0 --cflags --libs</command>
     </para>
     <para>When using autoconf and automake, this is even easier with the PKG_CHECK_MODULES macro in your 
configure.ac file. For instance:
     <programlisting>
-    PKG_CHECK_MODULES(SOMEAPP, libxml++-3.0 >= 3.0.0)
+    PKG_CHECK_MODULES(SOMEAPP, libxml++-4.0 >= 4.0.0)
     AC_SUBST(SOMEAPP_CFLAGS)
     AC_SUBST(SOMEAPP_LIBS)
     </programlisting>
diff --git a/libxml++/libxml++.h b/libxml++/libxml++.h
index 89cbf4e..81d8c8b 100644
--- a/libxml++/libxml++.h
+++ b/libxml++/libxml++.h
@@ -33,14 +33,14 @@
  *
  * If your source file is @c program.cc, you can compile it with:
  * @code
- * g++ program.cc -o program `pkg-config --cflags --libs libxml++-3.0`
+ * g++ program.cc -o program `pkg-config --cflags --libs libxml++-4.0`
  * @endcode
  * If your version of g++ is not C++11-compliant be default,
  * add the @c -std=c++11 or @c -std=c++0x option.
  *
  * Alternatively, if using autoconf, use the following in @c configure.ac:
  * @code
- * PKG_CHECK_MODULES([LIBXMLXX], [libxml++-3.0])
+ * PKG_CHECK_MODULES([LIBXMLXX], [libxml++-4.0])
  * @endcode
  * Then use the generated @c LIBXMLXX_CFLAGS and @c LIBXMLXX_LIBS variables in
  * the project @c Makefile.am files. For example:


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]