Hi, Trimmed responses below: >> Second, it wasn't really clear where I was meant to get xmllint from >> once it complained about that, after a failed attempt (xmllint.exe from >> googlecode) I ended up downloading a bunch of ZIP files from: >> ftp://ftp.zlatkovic.com/libxml/ >> And sticking the contents of the bin/ folder in C:\WINDOWS (for >> simplicity). You may want to add a link and brief explanation to the README. > > I've used a GTK+ runtime environment constructed manually from scratch > (basically, it contained everything now included with the 32-bit aio > installer except maybe glade) to bootstrap. OK, so I am going to have jhbuild the whole thing, right? Has it been done before on 64-bit? Is it even meant to work?
> After that, once you've got a complete aio version installed for > the Python version used to run build_installer.py, you have everything > (except WIX) needed (i've always executed build_installer.py with > Python 2.7 + PyGTK All-in-one 2.whatever.-the-latest-build-might-be). > Heh, once you're bootstrapped it's a bit of a self-hosting > environment ;) > > A 32-bit xmllint can be found in > http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2-dev_2.7.7-1_win32.zip > And a 64-bit version is included in > http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/libxml2-dev_2.7.7-1_win64.zip Hah! Much easier, thanks. > Thinking about it, maybe you could use a 32-bit Python 2.7 with a > 32-bit PyGTK-All-in-one (complete installation) to run the > build_installer.py script just to bootstrap build_installer for a > 64-bit build? This sounds a bit unclean, but it may be easier. (...) > I agree that's not a good long-term solution[1] , but with 2.24 being > the last PyGTK release ever[2] I won't bother changing build_installer > just yet... 2.24 was just released today, which makes it an ideal time to look into this. > The wix/2.23.1.win64.xml file is a skeleton build description file. (...) > You could use wix/2.23.1.win32.xml as an example here. Gotcha. > Note that 64-bit pycairo/pygobject/pygtk Python extension modules > will need to be built with the build_bindings.sh script backed by > a 64-bit GTK+ runtime, 64-bit Python and a MinGW64 toolchain. Why the MinGW64 toolchain? I thought that you needed to use VC2008 to ensure python modules can link to VC dlls used to build Python 2.x? (...) > [1] I've been playing with the idea to turn the whole project into a > more generic gnome-windows .msi installer generator. Just think about > the impact a good stand-alone Glade or whatever installer could > have. Guess the build description schema is going to have to evolve > even more! :) That's quite ambitious. When I find the time, I'll try to bootstrap at least GTK 64-bit and see how it goes from there. Can you just confirm whether I should be using MinGW or VC2008? Thanks Antoine _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
