Enable experimental GTK+ 3 test builds in Windows

> 1. Providing the required libraries in devlibs

Theoretically, we just need to add the required gtk3 and gtkmm3 libs, and share the other libs between gtk2 and gtk3 builds..
Unfortunately, gtk3 requires that we also update lots of our dependencies, starting with glib (the last time I checked, there were issues when compiling it on win32 with mingw).

Another option would be to use cross-compiled libs from OpenSuse (http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_12.2/noarch/). I did some tests last July. Inkscape compiled correctly but failed to run (see http://old.nabble.com/GTK%2B-3-build-complete-to33993847.html#a34230927). Very likely a compiler issue.

2. Providing suitable config file(s) in Inkscape

Almost all the changes need to be done in the build.xml file. Note that there are some deprecations in the win32 specific code (filedialogimpl-win32) and that gdl needs to be tweaked a bit.

> I guess we could provide a separate "testing" branch for windows

I'd rather provide a testing branch for the devlibs only, and provide a patch for the changes that need to be applied to Inkscape-trunk.

Some precisions:
* During my attempt, I didn't update everything in the devlibs, and the fact that our current libs were compiled with an old gcc version (opensuse ones are compiled with gcc-4.7) is probably the cause of the failure. I'll try again with a blank new devlib folder, with 4.7 libs only.
* The gdl fix is not a good idea. We should use external gdl libs instead...

@Nico - As far as I can tell, GTK+ 2 should work with most of the GTK+ 3 dependency versions (Glib 2.32 etc) so is there much point in having a separate branch?

Perhaps the most productive plan would be to first try bumping Glib, ATK etc to versions that are compatible with GTK+ 3. If the GTK+ 2 build still works OK, then we can move on to add GTK+ 3 and Gtkmm3 to devlibs without needing a separate branch.

Alex> GTK+ 2 should work with most of the GTK+ 3 dependency versions

Yes, but in the current devlibs, our dependencies are too old compared to the versions required by GTK+3. And some dependencies (particularly Glib 2.32) are somewhat difficult to compile on Windows with mingw. That's the reason why I'm currently trying to work with the OpenSuse cross-compiled libs.
If everything works fine with it, yes, we could just add GTK+2 and officially decide to switch to gcc-4.7 (we're currently stuck with 4.6, due to recent changes in the GCC ABI).

Ah OK... makes sense. :)

Just spent the day working on it and... it now runs!

Well, I've had to disable some features, such as aspell and imagemagick, compile libiconv (not cross-compiled at OpenSuse) and fix some extra gcc-4.7 related things in the code. But at least we can test it and it's a good start.

I still have to do some clean-up, update the documentation, fix things that are disabled, and create a new devlibs-gtk3 branch...

BTW, a testing binary version is available at ftp://download.tuxfamily.org/inkscape/inkscape-11951-gtk3-experimental.7z

JazzyNico: You might just be super awesome! Thanks for your work on this!

Great news :) Thanks for your hard work and expertise!

Jazz, can you commit your modified build.xml as "build-gtk3.xml" to trunk? Thanks!

@Johan - A diff file (inkscape-win32-gtk3.diff) is available in the devlibs-gtk3 branch (there are other things to change apart from the build.xml file).
I've also added some documentation (win32-gtk3.txt) on how to compile Inkscape and how to update the devlibs.

Note that it's still experimental, and that some features (ImageMagick and Aspell) don't work due to compilation issues, and other things (hicolor icons) need to be fixed.

Deprecations specific to the Win32 version are now fixed. The remaining diff file deals with GTK/GTKMM synchronization issue in the Opensuse repo.
There are still issues with ImageMagick (something wrong with the devlib package) and Aspell (not available in the repo, and difficult to compile on Windows XP), and some other bugs that I'm going to report separately.

Test version available: ftp://download.tuxfamily.org/inkscape/

Note that the experimental devlibs (https://code.launchpad.net/~jazzynico/inkscape-devlibs/devlibs-gtk3) also work with GTK2 (build.xml.gtk2).
I'm currently working on a 64 bits version of the experimental devlibs (no link yet), also based on the Opensuse cross-compiled files. But since I have no 64 bits Windows OS, I'll need some help from other devs to compile missing libs and test.

I could help test x64 builds once they are made. I'm running Windows 7 x64 here.

@rickmastfan67 - I'm currently working on a win64 version of the devlibs. I'll post here when it's ready to test.

Great Jazz! Look forward to testing inkscape-devlibs64 !

Win32/gtk3 branch updated to use the new Opensuse 12.3 files (gtk-3.8, glib-2.36 and lots of other updates).

Now that gtk and gtkmm use the same version number, we no longer need to patch the Inkscape code before compiling.

Due to lack of time, no progress on the Win64 branch...

Hi Nico, just wondering where we're up to with this? We now have Gtk+ 3 builds available for linux and the PPA, so it would be good to go ahead with devlibs whenever possible.

Hi Alex,
Unfortunately the Opensuse libs didn't change since my last update (at least the Cairo, Gtk and ImageMagick ones) and thus none of the known issues are fixed.
Apart from the libs update, I've noticed Opensuse now provide a cross-compiled version of Inkscape 0.48.4. I haven't tested it yet, but it would be interesting to see if it shows the same issues or not.

Devlibs-gtk3 updated with GCC-4.8.1 compiled libraries (r28). Tested with Inkscape trunk 12823, TDM-GCC-4.8.1.

ImageMagick still crashes (see bug #1252719 [devlibs-gtk3] Inkscape crashes with ImageMagick related commands ), and I have difficulties building aspell (see bug #1252711 [devlibs-gtk3] Compile Aspell with GCC-4.8.1).

But at least we (Johan helped me a lot!) managed to get rid of the GCC-4.8 related errors on Windows.

A test archive is available: ftp://download.tuxfamily.org/inkscape/inkscape-12823-gtk3-experimental.7z

Downloaded and it started in Windows 7 x64 SP1.

It did take forever (30+ seconds) to start up the first time when it was creating a new profile (didn't want my "tested" profile to be damaged).

Found a bug right away with the GUI (not present in the x86 trunk versions). How should I report it? Here in this bug, or as a separate bug and link you to it?

@rickmastfan67 - Thanks for your test!
You can create a new report in the devlibs project, tagged with gtk3, and add a link here.

@jazzynico Here you go: https://bugs.launchpad.net/inkscape-devlibs/+bug/1252936

Devlibs-gtk3 revision 31 now works with Aspell.

The ImageMagick crash is now the only (known...) blocker.

Any new test binaries for the current devel branch or release version (0.91)?

I am hoping to get the new HiDPI support in libgdk 3.

Planning to try makepkg'ing https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-inkscape/PKGBUILD later.

GTK3 builds are now possible with devlibs64 (starting with r29).
The necessary build file for btool (build-x64-gtk3.xml) was committed to Inkscape trunk in r14673.

Inkscape builds created this way [1] are far from being usable in production but at least there are no immediate crashes...

[1] a test build is available at https://drive.google.com/folderview?id=0B3IZiqBj23X1eG5JeVBaSFFTanM&tid=0B3IZiqBj23X1My1CaUE2NjlpVms#list

You should now be able to create trunk builds with CMake, too.
First test build is at [1].

http://download.tuxfamily.org/inkscape/win64/inkscape_trunk_r15113_win64.7z

MSYS2 builds [1] allow for building with GTK+ 3 for both win32 and win64, so I probably can close this eventually...

[1] http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_with_MSYS2

Yes, and there are probably lots of other bugs we could close thanks to MSYS2.
We could even close the whole devlibs branches.

True, but there are some things, we have to sort through first, notably
1. Make building with MSYS2 official for trunk (I think were pretty much there, though)
2. Decide if we want to switch to MSYS2 for 0.92.x branch, too.

For both I'd still like some more people getting involved in testing / giving feedback...

Switching in 0.92.x would obviously have advantages, but it would require some effort (also with respect to packaging), so we should not rush things.
On the other hand, if we decide to switch eventually, we should not wait for too long, to get extensive testing going as soon as possible.

If I get around to it I'll update 0.92.x branch to support building with MSYS2, push some testing builds and create a bug to track progress this weekend.

> 2. Decide if we want to switch to MSYS2 for 0.92.x branch, too.

Just had the opportunity to test today, and unfortunately, the MSYS2 package for 32-bit system doesn't seem to run on Windows XP (dwmapi.dll missing). The package was created on Windows 7 (64-bit), with mingw32. Unless I missed something important when building, we're stuck with the old devlibs for 0.92.x.

And I can also confirm that MSYS2 doesn't run on XP (the website claims it doesn't install, but I wanted to be sure it wasn't just an installer compatibility issue).

@jazzynico: You're talking about a gtk2 build of 0.92.x, right? (just to be sure as this bug is about GTK+ 3 in principle)

In fact my (32-bit) MSYS2 builds of 0.92.x (compiled on Windows 10 x64) seem to work just fine on a Windows XP x86 machine, see for example [1] which I just built.
Can you check if this version runs on your XP machine? Maybe we're lacking CMake build flags unless there's not another problem I'm not aware of...

> And I can also confirm that MSYS2 doesn't run on XP (the website claims it doesn't install, but I wanted to be sure it wasn't just an installer compatibility issue).

Can you clarify? Does it not work at all? As far as I know an NTFS volume is required for running MSYS, but from what I read it should also work on XP in principle.

[1] https://download.tuxfamily.org/inkscape/win32/inkscape-0.92.x-15414-win32_MSYS2.7z

> In fact my (32-bit) MSYS2 builds of 0.92.x (compiled on Windows 10 x64) seem to work just fine on a Windows XP x86 machine, see for example [1] which I just built.

Sorry I didn't test with the right files, but with a trunk version...
So I can confirm the linked archive runs correctly on Windows XP. And I'm really released it does.

As for MSYS2, the project's homepage says it doesn't install on XP. So I installed it (win32 version) on Windows 7, and then moved the folder to XP. The issue was reported in the MSYS2 bug tracker, and closed, unfortunately (see https://github.com/Alexpux/MSYS2-packages/issues/687).

Great, good to know 0.92.x binaries are executable on XP!

Thanks for the link regarding XP support of MSYS2. So it seems there's currently no real option to also compile on XP. (I only stumbled over the installer issues before, but if Cygwin dropped XP support, there's obviously not much that can be done...)

> eduard-braun2:
> So it seems there's currently no real option to also compile on XP.

As jazzynico mentioned before, MSYS2's programs themselves seem to work on Windows XP, and you can actually try moving the files to an XP computer. If MSYS2's pacman also works on XP, you should be able to live and build with it for a while before some core MSYS2 dll updates (a new installer run) becomes necessary.

I am somehow thinking about running it "the wine way", i.e. creating a fake kernel32.dll with a stub for CancelSynchronousIo to make Windows XP happy with the installer. That seems to require some injection magic and consequently an "installer launcher". Um, no.

With the MSYS2 build of 0.92.2 playing out nicely I think we can mark this resolved for Inkscape. Nightly builds with gtk3 work fine, see [1] for instructions.

devlibs/devlibs64 should be considered unmaintained/deprecated at this point.

[1] http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_with_MSYS2