~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to INSTALL

  • Committer: Sidnei da Silva
  • Date: 2009-07-03 15:06:42 UTC
  • mto: (4531.1.1 integration)
  • mto: This revision was merged to the branch mainline in revision 4532.
  • Revision ID: sidnei.da.silva@canonical.com-20090703150642-hjfra5waj5879cae
- Add top-level make target to build all installers using buildout and another to cleanup

Show diffs side-by-side

added added

removed removed

Lines of Context:
13
13
 
14
14
  http://www.lag.net/paramiko/
15
15
 
 
16
bzr can optionally use compiled versions of some parts of the code
 
17
for increased speed. When installing bzr you need the ability to
 
18
build C extensions. Some Linux distributions package the necessary
 
19
headers separately from the main Python package. This package is
 
20
probably named something like python-dev or python-devel. FreeBSD,
 
21
Windows, source-based Linux distributions, and possibly other operating
 
22
systems, have the required files installed by default.
 
23
 
 
24
If you are installing bzr from a bzr branch rather than a release tarball,
 
25
then you should also have the Pyrex package installed. This is not necessary
 
26
for release tarballs as they already contain the C files that Pyrex is needed
 
27
to create.
 
28
 
 
29
  http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/
 
30
 
16
31
Installation
17
32
------------
18
33