Hi John, and thank you so much for input! I'm building from MSVC project file, and have just now double checked everything.
I've already taken care of the "undef GTKMM_ATKMM_ENABLED" you mentioned, and replaced that line with either: #define GTKMM_ATKMM_ENABLED 1 or commented out: // #define GTKMM_ATKMM_ENABLED 1 First case gives runtime error when closing windows, second case (commented out) works fine. but I noticed some other thing, the comment above this macro says: /* Defined when the --enable-api-atkmm configure argument was given */ So by using some logic it looks that gtkmm is supposed to be built without atkmm support if building with msvc project file without doing *./configure** --enable-api-atkmm* first. therefore to build with atkmm support I'm also supposed to configure sources with --enable-api-atkmm first? Can somebody confirm this? I thought defining that macro to is enough to enable atkmm API's with gtkmm. Thank you so much! On Mon, Nov 16, 2015 at 7:28 PM, John Emmas <[email protected]> wrote: > Do you build Gtkmm from a command line or from an MSVC project? It's just > that I noticed this at line 7 of gtkmmconfig.h.in:- > > #undef GTKMM_ATKMM_ENABLED > > So I'd assume that if you're building from a VC project, the above symbol > will always be undef'd (even if your project file #defines it). I just > checked here and it does seem to be undef'd for me (even though it's > #defined in my project's preprocessor definitions!!) > > Just wondering how it's getting #defined at your end? Presumably you're > building from a command line? > > John > _______________________________________________ > gtkmm-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/gtkmm-list >
_______________________________________________ gtkmm-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtkmm-list
