More detailed build prerequisite instructions #319

Closed
wants to merge 2 commits into from

1 participant

@llimllib

Clarifying some things, based on suggestions from Alex on
#topaz.

  • Guide everybody to use virtualenv and virtualenvwrapper. The world will be happier for it.
  • direct people to use add2virtualenv instead of PYTHONPATH
  • note that the pypy dir must be added to your environment, not just the rpython dir (due to main importing py)
llimllib added some commits Feb 6, 2013
@llimllib llimllib More detailed build prerequisite instructions
Clarifying some things, based on suggestions from Alex on
#topaz.

* Guide everybody to use virtualenv and virtualenvwrapper.
  The world will be happier for it.
* direct people to use add2virtualenv instead of PYTHONPATH
* note that the pypy dir must be added to your environment,
  not just the rpython dir (due to __main__ importing py)
404e444
@llimllib llimllib improve getting-started capitalization and grammar 05675db
@alex alex commented on the diff Feb 7, 2013
docs/getting-started.rst
@@ -27,17 +27,19 @@ missing features. If you do please :doc:`report them </contributing>`!
Building Topaz
--------------
-Before you build Topaz, there's a few things you'll need:
-
-* A checkout of the topaz repository: ``git clone http://github.com/topazproject/topaz``
-* A recent checkout of the PyPy repository:
- ``hg clone https://bitbucket.org/pypy/pypy``
-* RPly: ``pip install -r requirements.txt``
-
-We recommend installing ``PyPy`` and ``RPly`` into a `virtualenv`_.
-
-Once everything is setup (make sure ``rpython`` is on your ``PYTHONPATH``), you
-can compile Topaz::
+Before you build topaz, you should:
+
+* Have virtualenv and virtualenvwrapper installed; otherwise:
+ ``pip install virtualenv virtualenvwrapper``
@alex
Topaz Project member
alex added a note Feb 7, 2013

I'm not sure we want to describe the whole process of setting up a virtualenv for this stuff, I'll have to think about this a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@llimllib

Closing because I ought to have done this on a branch, not on master.

@llimllib llimllib closed this Feb 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment