--enable-api-atkmm just defines GTKMM_ATKMM_ENABLED in
gtkmmconfig.h and config.h. That's all it does. And you don't have
to worry about config.h. It's not even distributed. I suppose you
don't use it. To choose between a build with or without atkmm
functionality, all you have to do is define or not define
GTKMM_ATKMM_ENABLED in gtkmmconfig.h, and recompile all files that
include gtkmmconfig.h. You mentioned in an earlier post that the error you see is a double deletion of some memory. I've never built gtkmm with MSVC myself, but I've understood that MSVC is better than gcc-compiled programs at detecting errors in allocation and deallocation of dynamic memory. Therefore I ran the toolbar example program in the gtkmm tutorial (which allocates some widgets on the heap) with valgrind. It reported some lost (leaked) memory. That's normal with programs that use glib and gtk+. No other memory problems. And I checked with gdb that Atk::Implementor::~Implementor() was called several times. Kjell Den 2015-11-17 kl. 06:18, skrev
codekiddy:
|