thanks for the confirmation andrew, then mypaint windows could have a longer breath
about the build_env, whether someone try from scratch or continue mine, I'd like to explain what it is
basically it contain:
- mingw (no msys) with gcc 32bit and gcc-cross64
- python 2.6 with py2exe and other python dependencies. in both 32bit and 64bit
note: gcc compatible import library need to be created first and patched python.h also needed for python64 (already done)
if you care about psyco, there is version 2.0.1 on the net that usable but only work with python 2.6 32bit
- GTK 2.24 runtime and devel. files in both 32 and 64 bit (If I recall the headers/pkgconfig versioning is screwed up)
note: it has freetype disabled cause I think it's not needed for mypaint, the current state still require json-c (both 32 and 64 bit)
note: the current installer script for mypaint is quite lame
At first I try to mimic inkscape build environment but since mypaint is way simpler I also bundling pretty much everything. Bunch of batch files needed for initialization though most of it should be moved to scons whenever possible. I think reading the batch files will pretty much will figure out how it work
how to update dependency:
if official win32 binary available, copy the bin/lib/share hierarchy into GTK/GTK64 folder, if it was python dependencies it usually can be copied directly to python/python64's site-packages folder.
unfortunately if no binary available, the build_env itself might not able to build it (if require autotooled chain), therefor a complete set of msys+mingw will be needed. This is beyond the scope thereafter, I assume you know what to do
My plan is to have someone maintained it in googlecode, upgrade the build_env into buildbot (integrate git and googlecode_uploader) then voila mypaint snapshot everyday and everyone will be happy
. Definitely I don't have the resource to do that.