Re: gtkmm 2.7.1

[Murray Cumming <murrayc murrayc com>]

On Wed, 2005-07-13 at 10:29 +0200, Daniel Holbach wrote:
> Hi everybody,
> 
> I have some questions about the new release:
> 
> 
> 1) How do I have to interpret ./NEWS:
> 	gtkmm 2.7 wraps new API in GTK+ 2.7, and is API/ABI-compatibile with gtkmm 2.4 and 2.6.
> 	The new API is unstable, until this become the API/ABI-stable gtkmm 2.8 when
> 	GTK+ 2.7 becomes the API-stable GTK+ 2.8.
> 
> Does it mean, that stuff will start breaking again with gtkmm-2.8.x

I don't quite understand the question. This is just like GTK+, but our
API is called 2.4 instead of 2.0. gtkmm 2.8 will be API stable. 2.9 will
contain new unstable API. API that has ever already been declared stable
(such as the API in 2.6) will never be broken.

>  and
> I can package this as gtkmm2.4-2.7.x still?

That would make sense, though unstable gtkmm versions should never be
packaged for stable versions of distros.

> 2) The NEWS file names a lot of added functions, but the only thing that
> changed in configure.in is:
> 
> daniel bert:~/new$ diff gtkmm2.4-2.6.3/configure.in gtkmm-2.7.1/configure.in
> 17,18c17,18
> < pushdef([GTKMM_MINOR_VERSION],     [6])
> < pushdef([GTKMM_MICRO_VERSION],     [3])
> ---
> > pushdef([GTKMM_MINOR_VERSION],     [7])
> > pushdef([GTKMM_MICRO_VERSION],     [1])
> 397a398,400
> >     examples/book/comboboxentry/Makefile
> >       examples/book/comboboxentry/text/Makefile
> >       examples/book/comboboxentry/complex/Makefile
> daniel bert:~/new$
> 
> Shouldn't this at least be a case for
> 
> # +1 : ? : +1  == new interface that does not break old one
> 
> in LIBGTKMM_SO_VERSION?

No, because that actually requires a recompile of applications to use
the new library. libtool versioning isn't so wonderful. For instance,
GTK+ _never_ changes that whole number.

> 3) Do you get the same build error?
> 
> cursor.cc: In constructor 'Gdk::Cursor::Cursor(const Glib::RefPtr<Gdk::Display>&, const Glib::ustring&)':
> cursor.cc:61: error: 'gdk_cursor_new_from_name' was not declared in this scope
> cursor.cc: In member function 'Glib::RefPtr<Gdk::Pixbuf> Gdk::Cursor::get_image()':
> cursor.cc:165: error: 'gdk_cursor_get_image' was not declared in this scope
> cursor.cc: In member function 'Glib::RefPtr<const Gdk::Pixbuf> Gdk::Cursor::get_image() const':
> cursor.cc:170: error: 'gdk_cursor_get_image' was not declared in this scope
> make[6]: *** [cursor.lo] Error 1
> make[6]: Leaving directory `/tmp/buildd/gtkmm2.4-2.7.1/gdk/gdkmm'
> make[5]: *** [all-recursive] Error 1

Maybe you don't have the latest GTK+, or I was using an unreleased
version from CVS?

> Sorry for so much trouble in one mail, but I'd really like to get the
> new gtkmm "out in the wild". :)

Thanks.

-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com