At Allmydata we used py2exe to build a (suite of) .exe file(s) including all the bundling of python libraries etc. It's not perfect (it doesn't integrate terribly well with .egg files for instance) but it works pretty well.
We also used InnoSetup to build setup.exe installers for all the pieces. So, that is to say, what you're asking about is a 'solved problem', or at least once was ;-) I'm not sure how much of that build stuff made it from .com into the open source tahoe repo (I'd look into it, but am busy on something else at the mo) but the above tools are to some extent "known to work". If you have questions, problems, feel free to ask me :-) cheers, rob On Jul 21, 2009, at 3:41 PM, Shawn Willden wrote: > Hi, > > I know that someone (sorry, don't recall who) was looking into > building and > installing Tahoe on Windows a while back. What's the status of that? > Assuming it works, how difficult is it? I'd like to start deploying > my own > friendnet with my family, and they're mostly on Windows. > > For the more experienced Pythonistas out there, what is the > recommended way to > create simple installation packages for Windows? I'm thinking about > creating > an MSI that includes the Python interpreter (2.6), all dependencies > and > Tahoe. Does that make sense? > > Thanks, > > Shawn. > _______________________________________________ > tahoe-dev mailing list > [email protected] > http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
