tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

implement the "Don't Repeat Yourself" principle 

[Imported from Trac: page AdvancedInstall, version 67]
zooko 2014-02-20 20:48:04 +00:00
parent 8dee5ccc55
commit 9f352cf738
1 changed files with 5 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
AdvancedInstall.md

@ -58,8 +58,6 @@ This isn't a complete list of dependencies though, because some of those package
`zope.interface: 3.5.0, simplejson: 2.0.7, pyutil: 1.3.30, zbase32: 1.1.1, allmydata-tahoe: 1.2.0-r3353, pyOpenSSL: 0.7, Twisted: 8.1.0-r25700, Nevow: 0.9.33-r17166, foolscap: 0.3.2, zfec: 1.4.2, pycryptopp: 0.5.12, argparse: 0.8.0, setuptools: 0.6c10dev` `zope.interface: 3.5.0, simplejson: 2.0.7, pyutil: 1.3.30, zbase32: 1.1.1, allmydata-tahoe: 1.2.0-r3353, pyOpenSSL: 0.7, Twisted: 8.1.0-r25700, Nevow: 0.9.33-r17166, foolscap: 0.3.2, zfec: 1.4.2, pycryptopp: 0.5.12, argparse: 0.8.0, setuptools: 0.6c10dev`
Prior to Tahoe-LAFS v1.9.0, users running on Microsoft Windows also needed to manually install [pywin32](https://sourceforge.net/projects/pywin32). This should no longer be needed.
<a name="point4"></a> <a name="point4"></a>
## Overview ## Overview
@ -294,35 +292,18 @@ Note that Xcode is quite large (2.5GB) so plan accordingly if you will need to d
<a name="point9.4"></a> <a name="point9.4"></a>
### Windows ### Windows
The following procedure will build and run Tahoe-LAFS on Windows. (This is basically source:docs/quickstart.rst and part of source:docs/running.rst with Windows-specific paths spelled out.) Follow source:docs/quickstart.rst andsource:docs/running.rst.
Note that this assumes that you install Python in the default location (C:\Python27 for Python 2.7.x), if you choose another location you'll need to adjust the instructions below:
1. Download and install Python 2.7.3 (the x86 or x86-64 MSI installer link) from <http://www.python.org/getit/releases/2.7.3/> . <a name="point9.4.1"></a>
#### What if that doesn't work?
2. Download the latest Tahoe-LAFS release from [//source/tahoe-lafs/releases/ <https://tahoe-lafs.org/source/tahoe-lafs/releases/>]. Unpack it in a convenient place, such as C:\tahoe-lafs.
3. Open a command prompt and cd to the top of the Tahoe-LAFS tree (e.g. `cd \tahoe-lafs`).
4. Run "`C:\Python27\python setup.py build`". Wait a bit until it stops working. Note that you need a working network connection because it will download various dependencies. Ignore any warnings.
5. Run "`C:\tahoe-lafs\bin\tahoe create-client C:\tahoelafsbase`". Choose an appropriate base directory.
6. Run "`notepad C:\tahoelafsbase\tahoe.cfg`" to edit your config file. After "`introducer.furl = `", paste in the FURL of the introducer for the grid you want to connect to. See [TestGrid](TestGrid) to get the FURL of the introducer for the testgrid.
7. Run "`C:\tahoe-lafs\bin\tahoe start C:\tahoelafsbase`". Your node will start running and connect to the grid. The Windows firewall may ask whether or not to allow Python to make network connections. Say yes.
`C:\Python27\python setup.py install` can also optionally be used as on other platforms.
[=#point9.4.1]
==== What if that doesn't work? ====
The build or install steps could result in an error that says a compiler is needed. If this happens and you are using Python 2.7, it is a packaging bug that should be reported to the tahoe-dev list. If you are using a different version of Python or want to compile the C/C++ components yourself, install the MinGW C/C++ compiler as follows (this only works for 32-bit Windows): The build or install steps could result in an error that says a compiler is needed. If this happens and you are using Python 2.7, it is a packaging bug that should be reported to the tahoe-dev list. If you are using a different version of Python or want to compile the C/C++ components yourself, install the MinGW C/C++ compiler as follows (this only works for 32-bit Windows):
1. Download and install MinGW from https://sourceforge.net/projects/mingw/files/ (the main installer linked from the big green download button). The installer will prompt you for what components to install. You need the base components plus g++. 1. Download and install MinGW from <https://sourceforge.net/projects/mingw/files/> (the main installer linked from the big green download button). The installer will prompt you for what components to install. You need the base components plus g++.
2. Early versions of 5.1.x of MinGW had a bug in the bundled Gnu assembler. If typing "`as --version`" at the command line gives "`GNU assembler (GNU Binutils) 2.20`", then you have an affected version. To fix this, download an upgrade to a newer version of MinGW which has `GNU assembler (GNU Binutils) 2.20.51.20100613` or later. 2. Early versions of 5.1.x of MinGW had a bug in the bundled Gnu assembler. If typing "`as --version`" at the command line gives "`GNU assembler (GNU Binutils) 2.20`", then you have an affected version. To fix this, download an upgrade to a newer version of MinGW which has `GNU assembler (GNU Binutils) 2.20.51.20100613` or later.
3. Configure distutils to use MinGW. If you have another C/C++ compiler installed, such as the cygwin one, distutils may default to using it instead of the mingw one. To configure distutils to use mingw32, create a file called [//trac/tahoe-lafs/raw-attachment/wiki/AdvancedInstall/distutils.cfg distutils.cfg] in `C:\Python27\lib\distutils`, and put in that file (you may also need to use the script from [https://mail.python.org/pipermail/python-dev/2004-January/041676.html this email] in order to "register" the mingw compiler): 3. Configure distutils to use MinGW. If you have another C/C++ compiler installed, such as the cygwin one, distutils may default to using it instead of the mingw one. To configure distutils to use mingw32, create a file called [//trac/tahoe-lafs/raw-attachment/wiki/AdvancedInstall/distutils.cfg distutils.cfg] in `C:\Python27\lib\distutils`, and put in that file (you may also need to use the script from [this email](https://mail.python.org/pipermail/python-dev/2004-January/041676.html) in order to "register" the mingw compiler):
``` ```
[build] [build]