diff options
| author | Kjell Ahlstedt <kjellahlstedt@gmail.com> | 2019-03-17 12:01:19 +0100 |
|---|---|---|
| committer | Kjell Ahlstedt <kjellahlstedt@gmail.com> | 2019-03-17 12:01:19 +0100 |
| commit | 9eb59b445384c3810a13e14cc0d4cb1665dfc61b (patch) | |
| tree | 7a50b33f4feeacfe6b0ad4c4c1d456f181856759 /glib/glibmm.h | |
| parent | c095eeaee5d498b26ff4fb59a97b1b4c3c7951b7 (diff) | |
| download | glibmm-9eb59b445384c3810a13e14cc0d4cb1665dfc61b.tar.gz | |
Change the ABI to glibmm-2.62
So we can use the 2.60 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.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/glib/glibmm.h b/glib/glibmm.h index 63ba058d..20e7203a 100644 --- a/glib/glibmm.h +++ b/glib/glibmm.h @@ -64,12 +64,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.60 giomm-2.60` + * g++ program.cc -o program `pkg-config --cflags --libs glibmm-2.62 giomm-2.62` * @endcode * * Alternatively, if using autoconf, use the following in @c configure.ac: * @code - * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.60 giomm-2.60]) + * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.62 giomm-2.62]) * @endcode * Then use the generated @c GLIBMM_CFLAGS and @c GLIBMM_LIBS variables in the * project Makefile.am files. For example: |