Since 4.0.8 the build has automatically enabled C defines like
GTK_DISABLE_DEPRECATED for anyone who was working from a Bazaar
checkout. These macros were not defined for people working from
releases, but it seemed a good idea for people hacking on the bindings
themselves.
I've just discovered that Ubuntu is shipping GTK 2.15 (and god knows
what else) in their J version, and so this was screwing up anyone trying
to causally build java-gnome on Ubuntu Jaunty from VCS.
I'm not super impressed about this, but to get around this I've changed
the previously elegant automatic solution to now be explicit.
If you run
$ ./configure strict
you'll get the -DGTK_DISABLE_DEPRECATED etc declarations passed to the
compiler.
Once GTK 2.16 is out sometime in the next 6 months then we'll do a pass
of getting everything ported to it and getting rid of anything that uses
such deprecated code. If someone with 2.15 wants to start working on
this now they're welcome to.
(ie, there's nothing wrong with starting to implement GtkOrientable;
it'd just have to be a bunch of no-ops for the bulk of cases until we
raise our minimum requirement to 2.16 once it's out)
AfC
Sydney
--
Andrew Frederick Cowie
Operational Dynamics is an operations and engineering consultancy
focusing on IT strategy, organizational architecture, systems
review, and effective procedures for change management: enabling
successful deployment of mission critical information technology in
enterprises, worldwide.
http://www.operationaldynamics.com/
Sydney New York Toronto London
|
