summaryrefslogtreecommitdiff
path: root/glib/glibmm.h
diff options
context:
space:
mode:
authorKjell Ahlstedt <kjellahlstedt@gmail.com>2019-09-18 16:20:46 +0200
committerKjell Ahlstedt <kjellahlstedt@gmail.com>2019-09-18 16:20:46 +0200
commit3d819821c4136dbdf64d9ef09906f57a789b41f4 (patch)
tree5fa0fd1914316403676860a508621dc666a493f7 /glib/glibmm.h
parent283d820c2655a4333e3ca1167fb72c522b1f6dc2 (diff)
downloadglibmm-3d819821c4136dbdf64d9ef09906f57a789b41f4.tar.gz
Change the ABI to glibmm-2.64
So we can use the 2.62 version numbers for stable releases in the glibmm-2.4 ABI series. 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. We've done similar ABI name changes several times before.
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 2bd92bb5..a7587d17 100644
--- a/glib/glibmm.h
+++ b/glib/glibmm.h
@@ -63,12 +63,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.62 giomm-2.62`
+ * g++ program.cc -o program `pkg-config --cflags --libs glibmm-2.64 giomm-2.64`
* @endcode
*
* Alternatively, if using autoconf, use the following in @c configure.ac:
* @code
- * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.62 giomm-2.62])
+ * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.64 giomm-2.64])
* @endcode
* Then use the generated @c GLIBMM_CFLAGS and @c GLIBMM_LIBS variables in the
* project Makefile.am files. For example: