add Test section (and renumber later sections)
[Imported from Trac: page AdvancedInstall, version 36]
davidsarah
parent
3d34a1ca99
commit
3c4c71abf6
|
|
@ -14,15 +14,16 @@
|
|||
<a href=#point6.5> 6.5. Apple Disk Image (dmg)</a><br>
|
||||
<a href=#point7>7. Installing From A Source Tree</a><br>
|
||||
<a href=#point7.1> 7.1. Creating a binary distribution From A Source Tree</a><br>
|
||||
<a href=#point8>8. Platform-specific Notes</a><br>
|
||||
<a href=#point8.1> 8.1. Debian/Ubuntu</a><br>
|
||||
<a href=#point8.2> 8.2. CentOS 5.4</a><br>
|
||||
<a href=#point8.2.1> 8.2.1 Dependencies</a><br>
|
||||
<a href=#point8.3> 8.3. MacOS</a><br>
|
||||
<a href=#point8.4> 8.4. Windows</a><br>
|
||||
<a href=#point8.4.1> 8.4.1. What if that doesn't work?</a><br>
|
||||
<a href=#point8.4.2> 8.4.2. How do I make it run as a Windows service?</a><br>
|
||||
<a href=#point8.4.3> 8.4.3. How do I make it run under a different user account?</a><br>
|
||||
<a href=#point8>8. Testing</a><br>
|
||||
<a href=#point9>9. Platform-specific Notes</a><br>
|
||||
<a href=#point9.1> 9.1. Debian/Ubuntu</a><br>
|
||||
<a href=#point9.2> 9.2. CentOS 5.4</a><br>
|
||||
<a href=#point9.2.1> 9.2.1 Dependencies</a><br>
|
||||
<a href=#point9.3> 9.3. MacOS</a><br>
|
||||
<a href=#point9.4> 9.4. Windows</a><br>
|
||||
<a href=#point9.4.1> 9.4.1. What if that doesn't work?</a><br>
|
||||
<a href=#point9.4.2> 9.4.2. How do I make it run as a Windows service?</a><br>
|
||||
<a href=#point9.4.3> 9.4.3. How do I make it run under a different user account?</a><br>
|
||||
|
||||
|
||||
|
||||
|
|
@ -218,10 +219,35 @@ This should create a `dist` directory containing the bb-frozen distribution.
|
|||
The [bbfreeze-users](https://groups.google.com/group/bbfreeze-users) Google
|
||||
group may be able to help with general questions about bb-freeze.
|
||||
|
||||
<a name="point8"></a>
|
||||
<a name="point9"></a>
|
||||
## Testing
|
||||
|
||||
Use `python setup.py test` to run the whole test suite. This will rebuild
|
||||
if necessary.
|
||||
|
||||
There are a few other supported ways to run tests:
|
||||
* `bin/tahoe debug trial`. This will *not* rebuild (if a build was needed,
|
||||
> some tests may fail). It accepts all of the same options as Twisted's `trial`
|
||||
> script; use `bin/tahoe debug trial --help` to see help for these.
|
||||
* `python setup.py trial` does the same thing as `bin/tahoe debug trial`,
|
||||
> although it doesn't support all of the `trial` options (and the test suite
|
||||
> must be specified using `-s`). It's supported mainly for backward
|
||||
> compatibility.
|
||||
* `make test` does the same thing as `python setup.py test`.
|
||||
* `make quicktest` does the same thing as `bin/tahoe debug trial`.
|
||||
|
||||
Running `trial` directly is not supported because it will not necessarily
|
||||
put the correct libraries (the same ones that would be used by `bin/tahoe`)
|
||||
on Python's `sys.path`.
|
||||
|
||||
To run a subset of the tests after making a source change that does not require
|
||||
a rebuild, `bin/tahoe debug trial <testsuite>` is the quickest option.
|
||||
|
||||
|
||||
<a name="point9"></a>
|
||||
## Platform-specific Notes
|
||||
|
||||
<a name="point8.1"></a>
|
||||
<a name="point9.1"></a>
|
||||
### !Debian/Ubuntu
|
||||
|
||||
Tahoe-LAFS is primarily developed on !Debian/Ubuntu machines. You can either build
|
||||
|
|
@ -229,26 +255,26 @@ from source (as described by this page), or download pre-compiled debian
|
|||
packages for several distributions. See the [DownloadDebianPackages](DownloadDebianPackages) page for
|
||||
details.
|
||||
|
||||
<a name="point8.2"></a>
|
||||
<a name="point9.2"></a>
|
||||
### CentOS 5.4
|
||||
|
||||
For installing in CentOS 5.4 you need this list of package:
|
||||
|
||||
yum install gcc python-devel sqlite-devel gcc-c++ openssl-devel
|
||||
|
||||
<a name="point8.2.1"></a>
|
||||
<a name="point9.2.1"></a>
|
||||
|
||||
<h4>Dependencies</h4>
|
||||
|
||||
cpp glibc-devel glibc-headers kernel-headers libgomp libstdc++-devel e2fsprogs-devel keyutils-libs-devel krb5-devel libselinux-devel libsepol-devel zlib-devel
|
||||
|
||||
<a name="point8.3"></a>
|
||||
<a name="point9.3"></a>
|
||||
### MacOS
|
||||
|
||||
You will need the standard Xcode development tools installed, or at least GCC in order to build some dependencies.<br>
|
||||
Note that Xcode is quite large (2.5GB) so plan accordingly if you will need to download it.
|
||||
|
||||
<a name="point8.4"></a>
|
||||
<a name="point9.4"></a>
|
||||
### Windows
|
||||
|
||||
The following procedure will build and run Tahoe-LAFS on Windows. (This is basically exactly the [docs/quickstart.html](http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html) procedure except with Windows-specific paths spelled out.)
|
||||
|
|
@ -272,7 +298,7 @@ Note that this assumes that you install Python in the default location (C:\Pytho
|
|||
|
||||
`C:\Python26\python setup.py install` can also optionally be used as on other platforms.
|
||||
|
||||
[=#point8.4.1]
|
||||
[=#point9.4.1]
|
||||
==== What if that doesn't work? ====
|
||||
|
||||
If the build or install steps result in an error that says a compiler is needed, install the MinGW C/C++ compiler as follows:
|
||||
|
|
@ -292,12 +318,12 @@ compiler=mingw32
|
|||
|
||||
After installing the compilers, repeat the above instructions from step 4 (using a new command prompt to make sure that the environment variable setting has taken effect).
|
||||
|
||||
<a name="point8.4.2"></a>
|
||||
<a name="point9.4.2"></a>
|
||||
#### How do I make it run as a Windows service?
|
||||
|
||||
<http://agiletesting.blogspot.com/2005/09/running-python-script-as-windows.html>
|
||||
|
||||
<a name="point8.4.3"></a>
|
||||
<a name="point9.4.3"></a>
|
||||
#### How do I make it run under a different user account?
|
||||
|
||||
1. Create the new user account if necessary.
|
||||
|
|
|
|||
Loading…
Reference in a new issue