glibmm / maemo and GLIBMM_ENABLE_PROPERTIES

[Luca Ognibene <luca ognibene gmail com>]

Hi! I'm trying to port inkscape (uses glibmm/gtkmm) to maemo (www.maemo.org).
After seeing that it doesn't compile i've discovered that glibmm and gtkmm
are compiled w/o some API in maemo. May i ask why? Optimization? Is
the speed/memory gain so strong and useful?
I'm not a c++ developer but i'm a full time developer on linux and i
wanted to port inkscape. I've ported a lot of other programs  w/o much
effort but this API difference between maemo and desktop pc in glibmm
is quite hard to fix for a non c++ developer.
I've fixed most obvious problem, but for example.. how can i fix this?

class ImageToggler : public Gtk::CellRendererPixbuf {
public:
 ImageToggler( char const* on, char const* off) :
   Glib::ObjectBase(typeid(ImageToggler)),
   Gtk::CellRendererPixbuf(),
   _pixOnName(on),
   _pixOffName(off),
   _property_active (*this, "active", false),
   _property_activatable(*this, "activatable", true),
   _property_pixbuf_on(*this, "pixbuf_on", Glib::RefPtr<Gdk::Pixbuf>(0)),
   _property_pixbuf_off(*this, "pixbuf_off", Glib::RefPtr<Gdk::Pixbuf>(0))

Errors are:
dialogs/layers-panel.cpp:76: error: class
`Inkscape::UI::Dialogs::ImageToggler' does not have any field named
`_property_active'

Do you plan to begin to compile glibmm/gtkmm with standard api anytime soon? 
Speed and memory in maemo tablets are going to increase, 
developer's free time is always short :)

ciao
Luca