GTK and GTKMM libs are out of sync

Assigning to myself.
My knowledge in compiling C++ binding libraries is quite low. Don't hesitate to help me or patch the devlibs if you've already manage to compile gtkmm on Windows.

Also requires updading:
* pangomm-2.28.4
* glibmm-2.28.2
* atkmm-2.22.6

For the record, I'm compiling with the usual TDM-GCC (4.6.1) environment, plus system commands (sh required to run ./configure) from a separate MSYS install (without MINGW32!).
So far I've managed to build pangomm, glibmm and atkmm, and successfully tested the binaries (by replacing the dll files in the Inkscape installation folder).

To do:
* compile gtkmm (in progress)
* compile and test inkscape with the new libs' headers and dlls.

Good progress today. Everything compiled correctly. Extra work was needed in giomm (dbus includes needed to be commented) and gtkmm (weird .gtkmm-2.4.pc file issue). Inkscape also needed an update to take the new gtkmm version into account (build.xml file).

Now, test time!
If everything is ok, I plan to commit the new libs next Thursday.

Good new, everything looks fine with the new libs. Except that I forgot to link libstdc++ statically, and Inkscape doesn't launch if the lib is not in the install directory. Rebuilding in progress...

Sounds great! Hopefully, we'll be able to drop the conditional support for GTK+ 2.22 soon. By my count, OpenSUSE 11.4 is the only tracked non-LTS linux distro that still doesn't provide GTK+ 2.24, and it reaches end-of-life within 3 weeks.

Not completely done yet. I've spent lots of time yesterday finding out that the old gtkmm libs were build with g++ 4.4 (stdc++ linked statically by default) and that g++ 4.6 links stdc++ dynamically by default. There's new option, -static-libstdc++, but it returns an error when used with TDM-GCC 4.6 and 4.7.
Thus I've built the libs with g++ 4.4 (looks ok when copying the dlls to an existing Inkscape installation), but since the same g++ version produces a compiler error when building Inkscape, I now need to rebuild Inkscape with g++ 4.6...

@Alex - I've also started to build gtk+3, but it requires that we update almost everything in the devlibs. I've managed to build some libs, but I'm stuck with an error when compiling glib. That said, I'm not sure the required updates won't affect the current devlibs. Maybe it could be safer to create a new branch.

Libs updated devlibs revision 36.

Trunk updated (in order to use gtkmm 2.24) revision 11810.

Reopening due to regressions in devlibs r36 (uncommitted).
See Bug #1069806 <https://bugs.launchpad.net/inkscape-devlibs/+bug/1069806>

Reported the lack of win32 binary upstream [1]. Hopefully they'll be able to advise us on whether an official binary will be released.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=686807

Thanks Alex!
I've just found out that one of the regressions that led me to uncommit the devlibs r36 is not due to the gtkmm stack update (see Bug #1070903 'Crash when saving a new document').
Anyway, I'm going to create a separate devlibs branch so that we can test it without risking to break something in the official trunk.

Of course, it would be easier if the Gnome team could provide Windows binaries...

New devlibs-testing branch created (https://code.launchpad.net/~jazzynico/inkscape-devlibs/devlibs-testing).
Note that the current revision has the same issues (see https://bugs.launchpad.net/bugs/1069806) I've noticed with devlibs r36.

Feel free to use it to test if it introduces other regressions (don't forget to add "#define WITH_GTKMM_2_24 1" in build.xml in the Inkscape trunk). I've already tested it (mainly the tools, extensions and drawing commands) but may have missed bugs (as I did for the File>Open one).
If there's no other issue, it could be interesting to investigate if we could find a workaround.

Needless to say I will also try to solve the issue in the libs directly.

Libs updated again in devlibs revision 36.
The two regressions were not related to the devlibs, and are now fixed in the trunk.

Trunk updated (in order to use gtkmm 2.24) revision 11864.

Branch updated, revision 9919.