<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Flexion.Org Blog &#187; compile</title>
	<atom:link href="http://blog.flexion.org/tag/compile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.flexion.org</link>
	<description>Bad grammar and typos for total strangers</description>
	<lastBuildDate>Tue, 17 Jan 2012 17:01:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Distributing closed source Python applications</title>
		<link>http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/</link>
		<comments>http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/#comments</comments>
		<pubDate>Thu, 29 Jan 2009 13:04:03 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[binary]]></category>
		<category><![CDATA[compile]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mac OS X]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.flexion.org/index.php/2009/01/29/distributing-closed-source-python-applications/</guid>
		<description><![CDATA[Last November we switched to Python as the principal language for all new software development projects at work, ditching Microsoft Visual C++ and PHP in the process Last Friday we released our first Python application to our customers for both Windows and Linux users. Although we make good use of Open Source software development tools [...]]]></description>
			<content:encoded><![CDATA[<div class="socialize-in-content" style="float:right;"><div class="socialize-in-button socialize-in-button-vertical"><g:plusone size="tall" href="http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/"></g:plusone></div><div class="socialize-in-button socialize-in-button-vertical"><iframe src="http://www.facebook.com/plugins/like.php?href=http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/&amp;layout=box_count&amp;show_faces=false&amp;width=&amp;action=like&amp;font=arial&amp;colorscheme=light&amp;height=65" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:px !important; height:65px;" allowTransparency="true"></iframe></div><div class="socialize-in-button socialize-in-button-vertical"><a href="http://twitter.com/share" class="twitter-share-button" data-url="http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/" data-text="Distributing closed source Python applications" data-count="vertical" data-via="@flexiondotorg" data-related="@flexiondotorg"><!--Tweetter--></a></div><div class="socialize-in-button socialize-in-button-vertical"><script type="in/share" data-url="http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/" data-counter="top"></script></div></div><p>Last November we switched to <a href="http://www.python.org/" target="_blank">Python</a> as the principal language for all new software development projects at work, ditching Microsoft Visual C++ and PHP in the process <img src='http://blog.flexion.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Last Friday we released our first Python application to our customers for both Windows and Linux users.</p>
<p>Although we make good use of Open Source software development tools and methodologies the application we have just written is propritary and the source can not be released publically, therefore we needed to compile, or <i>freeze</i>, the Python script in order to create a stand alone executable. Tools that do this have been around for sometime, however our application makes use of Win32 Extensions for Python and WMI on Windows, DBUS/HAL on Linux, wxPython on both, and a number of other modules. This is quite a big ask for the Python script compilers and initially the only tool which could build this lot successfully was <a href="http://www.py2exe.org/" target="_blank">py2exe</a>. Sadly that only solves part of the problem since it is a Windows only tool <img src='http://blog.flexion.org/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>Then we found <a href="http://pypi.python.org/pypi/bbfreeze/" target="_blank">bbfreeze</a>, which supports both Windows and Linux with Mac OS X support being actively developed. bbfreeze has a simple build API and we were soon using it to build stand alone exectuables for both Windows and Linux. Everything is peachy, all we needed was as means to install our application.</p>
<p>Enter <a href="http://www.installjammer.com/" target="_blank">InstallJammer</a>. InstallJammer is a multiplatform GUI installer designed to be completely cross-platform and functions on Windows, most versions of UNIX with support for MacOS X coming soon. Perfect! We have now packaged our application using InstallJammer to create simple <i>Next, Next, Finish</i> installers which look and function the same on both Windows and Linux.</p>
<p>In the fullness of time we are planning to release our application on Mac OS X too, by that time we anticiapte that bbfreeze and InstallJammer will be upto speed with support for that platform. Just thought I&#8217;d share our experiences and I&#8217;d be interested to hear from anyone who has had to do the something similiar and what tools they used?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.flexion.org/2009/01/29/distributing-closed-source-python-applications/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

