diff options
author | Kjell Ahlstedt <kjellahlstedt@gmail.com> | 2020-03-17 14:46:43 +0100 |
---|---|---|
committer | Kjell Ahlstedt <kjellahlstedt@gmail.com> | 2020-03-17 14:46:43 +0100 |
commit | c817a5a9c2e38632de2e685a558f386aab8d7505 (patch) | |
tree | 422b3ae9353bb8084fdebaa5554b085e10798ecf /glib | |
parent | a6d6b6836db36e2e5a1e9d33b11482eb75fd9468 (diff) | |
download | glibmm-c817a5a9c2e38632de2e685a558f386aab8d7505.tar.gz |
Change the ABI to glibmm-2.66
So we can use the 2.64 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')
-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 93e3a4ff..7c17ebd0 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.64 giomm-2.64` + * g++ program.cc -o program `pkg-config --cflags --libs glibmm-2.66 giomm-2.66` * @endcode * * Alternatively, if using autoconf, use the following in @c configure.ac: * @code - * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.64 giomm-2.64]) + * PKG_CHECK_MODULES([GLIBMM], [glibmm-2.66 giomm-2.66]) * @endcode * Then use the generated @c GLIBMM_CFLAGS and @c GLIBMM_LIBS variables in the * project Makefile.am files. For example: |