Thanks for the links. I have read everything and I think I'll go for the cross compiling stuff from a linux vm, as it might be easier than setting everything up on windows (I actually have to install the VM, but it should be np as I have some live CD iso around of linux mint I think).
Now some questions about logistics: So you fixed the first part of the bug (A) and BenJackson found a solution for part (B). So if I manage to successfully setup the build environment for GTK+, then apply your patch, should I apply BenJackson's patch too, then get into investigating C, or further investigate B because BenJackson's fix is just a hack? Also (warning: open source development newbie question): When will your patch and BenJackson's patch (if it is the real answer to the problem) will be committed to the 2.24 branch of gtk+? Do you have to submit them first, or you will wait until the whole bug is fixed, or how does these things work? Mihai On Mon, Oct 10, 2011 at 1:23 PM, Martin Renold <[email protected]> wrote: > hi Mihai > > Nice to see some new interest in fixing MyPaint on Windows! Here are some > pointers. > > The main bugreport: > https://bugzilla.gnome.org/show_bug.cgi?id=653437 > > Setting up a GTK build environment usually takes around two days. You will > want to work on the git version of GTK (gtk-2-24 branch). > > The IRC discussion I had with BenJackson might be helpful if you want to > compile GTK using jhbuild (look around 08:06): > http://irclogs.jackgrigg.com/irc.freenode.net/mypaint/2011-08-13 > > It is probably possible to build GTK on Windows natively, but I haven't > tried myself because I am more familiar with the Linux toolchain. > > If you need support for building GTK, try to ask on MyPaint IRC or on the > GTK channel of the Gnome IRC network. People might be busy though, so it > can take time to get a response. > > Regards > Martin > > On Mon, Oct 10, 2011 at 11:14:12AM +0300, Mihai Cozma wrote: > > OK, I'll start working on it then when I'll get home from work. I'll keep > > you updated. > > > > > > On Mon, Oct 10, 2011 at 3:00 AM, Jon Nordby <[email protected]> wrote: > > > > > On 10 October 2011 00:43, Mihai Cozma <[email protected]> wrote: > > > > Thanks for the reply, useful links. > > > > I also found the next text there: > > > > "The plan seems to wait GTK 3.x become stable for win32 which takes > > > sometime > > > > which ultimately invalidate this instruction as we will go with PyGI > > > instead > > > > of PyGTK which is also another problem because GI isn't ported to > win32 > > > yet. > > > > That's the pity situation for mypaint win32." > > > > So based on this information, is there any point in trying to fix > bugs > > > and > > > > stuff, or we just have to wait until GI gets ported to windows and > gtk 3 > > > is > > > > stable for windows and so on? I mean, would all the work done trying > to > > > fix > > > > the problem in 2.24 get obsolete by the time GTK 3.x and this GI gets > > > used? > > > Fixing the critical/blocking issues in GTK 2.x on Windows is very > > > valuable still. > > > > > > Porting MyPaint to PyGI and GTK 3.x will likely not happen for the > > > next release. Meaning that without GTK 2.x fixed it will be some > > > additional months _after_ we get the next release out before Windows > > > will get the new stuff. > > > There are other projects that will benefit from having GTK 2.24 fixed > > > as well. GIMP 2.8 is another release that is also blocking on > > > this/these tablet bugs. > > > > > > And, I would not be totally surprised if fixes are also applicable to > GTK > > > 3.x > > > -- > > > Jon Nordby - www.jonnor.com > > > > > > _______________________________________________ > > Mypaint-discuss mailing list > > [email protected] > > https://mail.gna.org/listinfo/mypaint-discuss > > > -- > Martin Renold >
_______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
