summaryrefslogtreecommitdiff
path: root/glib/glibmm.h
diff options
context:
space:
mode:
authorMurray Cumming <murrayc@murrayc.com>2017-08-25 11:19:07 +0200
committerMurray Cumming <murrayc@murrayc.com>2017-08-25 11:19:07 +0200
commit9f89221b024b028286bea35f7a4d9b873bfb3266 (patch)
treefbda7c3aff3a6f0abef9fc55ca130badb9323b42 /glib/glibmm.h
parentdbf53fdad1133aa6f6966f2ef2fbbaafa4da3340 (diff)
downloadglibmm-9f89221b024b028286bea35f7a4d9b873bfb3266.tar.gz
Change the ABI to glibmm-2.54
So we can use the 2.53/54 version numbers for more stable releases. We don't need to release a stable ABI-parallel glibmm until we need to release gtkmm 4.0, and that won't happen until GTK+ 4.0.0 happens, and we don't know when that might be. We did this once before: https://git.gnome.org/browse/glibmm/commit/?id=dee483b29bdaaabc587f3f8b6bff05663e7dccdc
Diffstat (limited to 'glib/glibmm.h')
-rw-r--r--glib/glibmm.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/glib/glibmm.h b/glib/glibmm.h
index a9e90e02..101b80ed 100644
--- a/glib/glibmm.h
+++ b/glib/glibmm.h
@@ -65,12 +65,12 @@
*
* If your source file is @c program.cc, you can compile it with:
* @code
- * g++ program.cc -o program `pkg-config --cflags --libs glibmm-2.54 giomm-2.54`
+ * g++ program.cc -o program `pkg-config --cflags --libs glibmm-2.56 giomm-2.56`
* @endcode
*
* Alternatively, if using autoconf, use the following in @c configure.ac:
* @code
- * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.54 giomm-2.54])
+ * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.56 giomm-2.56])
* @endcode
* Then use the generated @c GLIBMM_CFLAGS and @c GLIBMM_LIBS variables in the
* project Makefile.am files. For example: