<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jhbuild on John Stowers</title><link>https://johnstowers.co.nz/tags/jhbuild/</link><description>Recent content in Jhbuild on John Stowers</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 16 Dec 2007 10:01:50 +0000</lastBuildDate><atom:link href="https://johnstowers.co.nz/tags/jhbuild/index.xml" rel="self" type="application/rss+xml"/><item><title>Jhbuild Anything on Windows - In 12 Steps</title><link>https://johnstowers.co.nz/2007/12/16/jhbuild-anything-on-windows-in-12-steps/</link><pubDate>Sun, 16 Dec 2007 10:01:50 +0000</pubDate><guid>https://johnstowers.co.nz/2007/12/16/jhbuild-anything-on-windows-in-12-steps/</guid><description>&lt;h2 id="part-1-the-complete-gtk-stack-from-source"&gt;Part 1: The Complete Gtk+ Stack from Source&lt;/h2&gt;
&lt;p&gt;Its been a long week spent watching things compile [0], but I&amp;rsquo;m happy to report that Jhbuild is now able to build the complete [1] stable Gtk+ stack on windows using the msys/mingw tool chain. That literally means that you can now build you Gtk app, or Gtk itself, for windows, in 12 steps. You still getting all the normal benefits that Jhbuild allows. So, the steps are;&lt;/p&gt;</description></item><item><title>Jhbuild and Windows - We Meet Again</title><link>https://johnstowers.co.nz/2007/12/13/jhbuild-and-windows-we-meet-again/</link><pubDate>Thu, 13 Dec 2007 01:56:18 +0000</pubDate><guid>https://johnstowers.co.nz/2007/12/13/jhbuild-and-windows-we-meet-again/</guid><description>&lt;h3 id="the-good-news"&gt;The Good News&lt;/h3&gt;
&lt;p&gt;Following on from &lt;a href="http://www.johnstowers.co.nz/blog/index.php/2007/12/11/jhbuild-adventures-on-windows/" rel="noopener"&gt;my last post&lt;/a&gt;
 I have continued work on getting Jhbuild to run on windows (within msys). The basic problem which I identified in my last post was the struggle between Python (for Windows) expectations about paths, and the hoops that msys and cygwin jump through to allow unix style paths to be used. Basically os.path.join and friends do the correct thing providing the subsequent path is used within python alone. Things get all difficult when that path is then passed out to a configure script, or as an argument to a shell command. With that in mind however, a picture speaks a thousand words&amp;hellip;.&lt;/p&gt;</description></item><item><title>Jhbuild Adventures on Windows</title><link>https://johnstowers.co.nz/2007/12/11/jhbuild-adventures-on-windows/</link><pubDate>Tue, 11 Dec 2007 19:20:18 +0000</pubDate><guid>https://johnstowers.co.nz/2007/12/11/jhbuild-adventures-on-windows/</guid><description>&lt;p&gt;&lt;strong&gt;Background:&lt;/strong&gt;
I&amp;rsquo;m going home to my parents house for Christmas, and because I don&amp;rsquo;t have a laptop, I thought it would be the perfect opportunity to use their computer to get &lt;a href="http://www.conduit-project.org/" rel="noopener"&gt;Conduit&lt;/a&gt;
 working on windows. However I could not find windows builds of (&lt;a href="http://developer.berlios.de/projects/pygoocanvas/" rel="noopener"&gt;py&lt;/a&gt;
)&lt;a href="http://sourceforge.net/projects/goocanvas" rel="noopener"&gt;goocanvas&lt;/a&gt;
 anywhere. Never minding a challenge I thought it would be a good experiment to see if I could build pygoocanvas for windows via cross-compilation or natively - both using &lt;a href="http://live.gnome.org/Jhbuild" rel="noopener"&gt;jhbuild&lt;/a&gt;
.&lt;/p&gt;</description></item></channel></rss>