Hi,
Le Dimanche 10 janvier 2016 22h57, Eduard Braun <Eduard.Braun2@...173...> a écrit :
Did you also consider giving the 64bit devlibs some love while you're at it?
My main computer is on Xubuntu 15.10, and I only have one official Windows XP (32bit) license, installed in a Virtualbox -mainly for testing Inkscape and updating devlibs. But I have no 64bit Windows that I could use to work on 64bit devlibs, sorry.
#### That said, we currently rely on a quite old TDM-GCC 4.6 version, and updating the devlibs is a manual and tedious process. It would be great if we could improve the way we maintain our devlibs, and somewhat automate it if possible. I'm currently investigating some possibilities, and MSYS2 (sourceforge.net/projects/msys2/) seems to be a good one -it already provides some of our dependencies (and, well, Inskcape 0.91 itself, see http://sourceforge.net/p/msys2/wiki/Packages/) and gives nice tools to build custom packages. Of course, we can also use TDM-GCC-5.1 with MSYS or maybe with MSYS2. Or use cross-compiled libraries such as the ones provided by OpenSuse (my old gtk3 test branch still works, see https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3). To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some): * The new devlibs must be easier to maintain compared to the current ones. * It should be possible to use the same steps to update win32 and win64 devlibs. * If both devlibs could provide exactly the same packages versions, it would greatly help bug tracking (and fixing)... * Do we still need to link libstdc++ statically? (Opensuse cross-compiled packages need a shared library.)
Regards, -- Nicolas