tahoe-lafs/docs/windows.rst

89 lines
3.0 KiB
ReStructuredText
Raw Normal View History

2016-03-26 00:27:38 +00:00
Building Tahoe-LAFS on Windows
==============================
You'll need ``python``, ``pip``, and ``virtualenv``. But you won't need a
compiler.
2016-03-26 00:27:38 +00:00
Preliminaries
-------------
1: Install Python-2.7.11 . Use the "Windows x86-64 MSI installer" at
2016-03-26 02:21:43 +00:00
https://www.python.org/downloads/release/python-2711/
2016-03-26 00:27:38 +00:00
2: That should install ``pip``, but if it doesn't, look at
2016-03-26 02:21:43 +00:00
https://pip.pypa.io/en/stable/installing/ for installation instructions.
2016-03-26 00:27:38 +00:00
3: Install ``virtualenv`` with
2016-03-26 02:21:43 +00:00
https://virtualenv.pypa.io/en/latest/installation.html
2016-03-26 00:27:38 +00:00
Installation
------------
1: Start a CLI shell (e.g. PowerShell)
2016-03-26 00:27:38 +00:00
2016-03-26 02:21:43 +00:00
2: Create a new virtualenv. Everything specific to Tahoe will go into this.
You can use whatever name you like for the virtualenv, but example uses
"venv"::
2016-03-26 00:27:38 +00:00
PS C:\Users\me> virtualenv venv
New python executable in C:\Users\me\venv\Scripts\python.exe
2016-03-26 00:27:38 +00:00
Installing setuptools, pip, wheel...done.
>
3: Use the virtualenv's ``pip`` to install the latest release of Tahoe-LAFS
into this virtualenv::
2016-03-26 00:27:38 +00:00
PS C:\Users\me> venv\Scripts\pip install --find-links=https://tahoe-lafs.org/deps/ tahoe-lafs
2016-03-26 00:27:38 +00:00
Collecting tahoe-lafs
...
Installing collected packages: ...
Successfully installed ...
>
2016-03-26 00:27:38 +00:00
4: Verify that Tahoe was installed correctly by running ``tahoe --version``,
using the ``tahoe`` from the virtualenv's Scripts directory::
2016-03-26 00:27:38 +00:00
PS C:\Users\me> venv\Scripts\tahoe --version
2016-03-26 00:27:38 +00:00
tahoe-lafs: 1.11
foolscap: ...
Running Tahoe-LAFS
------------------
The rest of the documentation assumes you can run the ``tahoe`` executable
just as you did in step 4 above. If you want to type just ``tahoe`` instead
of ``venv\Scripts\tahoe``, you can either "`activate`_" the virtualenv (by
running ``venv\Scripts\activate``, or you can add the Scripts directory to
your ``%PATH%`` environment variable.
2016-03-26 00:27:38 +00:00
Now use the docs in :doc:`running` to learn how to configure your first
Tahoe node.
2016-03-26 00:27:38 +00:00
.. _activate: https://virtualenv.pypa.io/en/latest/userguide.html#activate-script
2016-03-26 00:27:38 +00:00
Installing A Different Version
------------------------------
The ``pip install tahoe-lafs`` command above will install the latest release
2016-03-26 02:21:43 +00:00
(from PyPI). If instead, you want to install from a git checkout, then run
the following command (using pip from the virtualenv, from the root of your
git checkout)::
2016-03-26 00:27:38 +00:00
$ venv\Scripts\pip install --find-links=https://tahoe-lafs.org/deps/ .
2016-03-26 00:27:38 +00:00
2016-03-26 02:21:43 +00:00
If you're planning to hack on the source code, you might want to add
``--editable`` so you won't have to re-install each time you make a change.
2016-03-26 00:27:38 +00:00
Dependencies
------------
2016-03-26 02:21:43 +00:00
Tahoe-LAFS depends upon several packages that use compiled C code, such as
zfec, pycryptopp, and others. This code must be built separately for each
platform (Windows, OS-X, and different flavors of Linux).
2016-03-26 00:27:38 +00:00
2016-03-26 02:21:43 +00:00
Pre-compiled "wheels" of all Tahoe's dependencies are hosted on the
tahoe-lafs.org website in the ``deps/`` directory. The ``--find-links=``
argument (used in the examples above) instructs ``pip`` to look at that URL
for dependencies. This should avoid the need for anything to be compiled
during the install.