OK, I gave up on Linux cross compiling of GTK+ after trying for 3 hours to build gdk-pixbuf (I managed to build glib as instructed in the irc chat dump btw). Everything seems to be a complete mess. The last error I've got resumes to:
"We need Glib >= 2.27.2, pkg-config reported 2.28.1 and we found 2.28.6, so we fail on autoconf.sh." Now why would it do such a thing, since it got what it needed? Anyway. Hopefully I'll be able to configure a build environment on Windows, it's my only hope. I'm kind of disappointed a bit that such big and popular projects like the ones related to GTK are such a mess in terms of maintenance and you have to make such a big effort to configure environment for building them. It is sad that every time I try to build something it keeps failing on various dependencies, and I have to go google the error to get the name of the actual package I have to install. Fingers crossed for building it on Windows now... :) On Tue, Oct 11, 2011 at 5:56 PM, Mihai Cozma <[email protected]> wrote: > Done, https://bugzilla.gnome.org/show_bug.cgi?id=653437#c11 :) > > On Tue, Oct 11, 2011 at 5:48 PM, Jon Nordby <[email protected]> wrote: >> On 11 October 2011 15:54, Mihai Cozma <[email protected]> wrote: >>> I've re-read today all the comments around >>> https://bugzilla.gnome.org/show_bug.cgi?id=653437 of gtk 2. >>> So it looks like issue A is fixed, issue B is almost fixed by >>> BenJackson and issue C is fixed by setting >>> GDK_NATIVE_WINDOWS=1. >>> >>> Suppose B gets fixed, is there anything wrong in having >>> GDK_NATIVE_WINDOWS set to 1 for Windows? >>> Or it is not set that way in the official binaries so we have to look >>> another way of fixing it and the option >>> is there only for debugging/testing purposes? >> These comments/questions should got to GTK developers. For instance on >> the bug-report. :) >> >> -- >> Jon Nordby - www.jonnor.com >> > _______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
