binary package for win32 #242

New Issue

zooko · 2007-12-21T16:48:39Z

zooko commented

2007-12-21 16:48:39 +00:00

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.

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.

zooko added the

labels 2007-12-21 16:48:39 +00:00

zooko commented

2007-12-21 18:42:58 +00:00

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.

tahoe-lafs added this to the 0.8.0 (Allmydata 3.0 Beta) milestone 2008-01-23 02:41:07 +00:00

zooko modified the milestone from 0.8.0 (Allmydata 3.0 Beta) to 0.9.0 (Allmydata 3.0 final)

2008-03-08 02:14:04 +00:00

robk commented

2008-03-12 19:22:56 +00:00

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)

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)

tahoe-lafs added the

fixed

label 2008-03-12 19:22:56 +00:00

tahoe-lafs closed this issue

2008-03-12 19:22:56 +00:00

Sign in to join this conversation.