tag:blogger.com,1999:blog-19026079.post115894066052765883..comments2009-07-07T20:01:58.491+02:00Hanno Schlichtinghttp://www.blogger.com/profile/02880767944793425548hannosch@gmail.comBlogger2125tag:blogger.com,1999:blog-19026079.post-84447802038359647602009-07-07T20:01:58.491+02:002009-07-07T20:01:58.491+02:00Excellent post! I was in a rush and missed wininst the first time around but after a quick google I read this and had my installer built.<br /><br />You wouldn&#39;t happen to know where the source for cli.exe and gui.exe exist do you?<br /><br />Thank You,<br />Joseph ArmbrusterJoseph Armbrusterhttp://www.blogger.com/profile/16733688842342811675noreply@blogger.comtag:blogger.com,1999:blog-19026079.post-64998781516232517402006-11-18T01:41:00.000+01:002006-11-18T01:41:00.000+01:00Hi Hanno,<br /><br />I might be wrong, but I believe 'bdist_wininst' works on non-Windows systems as well, as long as you have pure python modules. You should double-check that.<br /><br />http://www.python.org/doc/2.4.3/dist/postinstallation-script.html<br />"""<br />If you have a pure module distribution (only containing pure Python modules and packages), the resulting installer will be version independent and have a name like foo-1.0.win32.exe. These installers can even be created on Unix or Mac OS platforms.<br />"""<br /><br />There's some information about building extensions with MingW32 too:<br />http://kampfwurst.net/python-mingw32/sidneihttp://www.blogger.com/profile/15767502023743866320noreply@blogger.com