#242 closed enhancement (fixed)

binary package for win32

Reported by: zooko Owned by: robk
Priority: major Milestone: 0.9.0 (Allmydata 3.0 final)
Component: packaging Version: 0.7.0
Keywords: win32 Cc: arch_o_median
Launchpad Bug:

Description

It would be nice to build binary packages for Windows so that people can install tahoe without compiling anything.

Simply running "./setup.py bdist_wininst" will create an installer for Tahoe. It will not include all of tahoe's dependencies in the resulting package -- that is the subject of another ticket.

Change History (4)

comment:1 Changed at 2007-12-21T18:42:58Z by zooko

  • Cc arch_o_median added

ticket #243 -- "package including all dependencies for win32" is the ticket about packaging all Tahoe's dependencies so that you can install one package and run it. This ticket is merely about shipping a binary so that you can install all the dependencies yourself, then install the binary, then run it without compiling it.

comment:2 Changed at 2008-01-23T02:41:07Z by secorp

  • Milestone changed from 0.7.1 to 0.8.0 (Allmydata 3.0 Beta)
  • Owner changed from somebody to robk

comment:3 Changed at 2008-03-08T02:14:04Z by zooko

  • Milestone changed from 0.8.0 (Allmydata 3.0 Beta) to 0.9.0 (Allmydata 3.0 final)

comment:4 Changed at 2008-03-12T19:22:56Z by robk

  • Resolution set to fixed
  • Status changed from new to closed

the make windows-exe build target will run py2exe over the tahoe sources and produce (in windows/dist) a binary package which can be run without any dependencies on python or on libraries being installed

it builds

  • tahoesvc.exe a windows service which contains a tahoe node
  • tahoe.exe a command line tool a la bin/tahoe, including 'tahoe run'
  • confwiz.exe a gui tool to bootstrap configuration for the allmydata service offering

tahoesvc looks in the registry to find its node root, under "Software/Allmydata/Base? Dir Path" in either HKLM or HKCU

tahoe run is provided for custom deployment situations where more control is desired. it looks in CWD by default for its noderoot, and runs synchronously (i.e. no daemonisation). this allows for e.g. multiple nodes to be run

confwiz defaults to configuring against the allmydata service, but takes a --server URL argument, and will configure itself based on any webserver providing the 'native_client' api

(all python code resides in 'library.zip' and all dependent binary libraries are placed alongside the .exe files. c.f. #195)

Note: See TracTickets for help on using tickets.