[pypy-svn] r16791 - pypy/release/0.7.x/pypy/doc

[arigo at codespeak.net]

Author: arigo
Date: Sat Aug 27 17:43:12 2005
New Revision: 16791

Modified:
   pypy/release/0.7.x/pypy/doc/faq.txt
   pypy/release/0.7.x/pypy/doc/getting-started.txt
Log:
Describe how translate_pypy produces a 'pypy-c' executable, including in the
FAQ, but warn loudly about this not being suitable for
installation/redistribution.



Modified: pypy/release/0.7.x/pypy/doc/faq.txt
==============================================================================
--- pypy/release/0.7.x/pypy/doc/faq.txt	(original)
+++ pypy/release/0.7.x/pypy/doc/faq.txt	Sat Aug 27 17:43:12 2005
@@ -36,4 +36,12 @@
     a full and compliant Python 2.4 interpreter.  RPython is only
     the language in which parts of PyPy itself are written.
 
+How do I compile PyPy?
+
+    See the `getting-started`_ guide.  Note that at the moment this
+    produces an executable that contains a lot of things that are
+    hard-coded for your particular system (including paths), so it's
+    not really suitable for being installed or redistributed.
+
 .. _`RPython`: coding-guide.html#rpython
+.. _`getting-started`: getting-started.html

Modified: pypy/release/0.7.x/pypy/doc/getting-started.txt
==============================================================================
--- pypy/release/0.7.x/pypy/doc/getting-started.txt	(original)
+++ pypy/release/0.7.x/pypy/doc/getting-started.txt	Sat Aug 27 17:43:12 2005
@@ -421,6 +421,14 @@
     2
     >>>> 
 
+With the default options, you can find the produced executable under the
+name ``pypy-c``.  Type ``pypy-c --help`` to see the options it supports --
+mainly the same basic options of CPython.  In addition, ``pypy-c --info``
+prints the translation options that where used to produce this particular
+executable.  This executable contains a lot of things that are hard-coded
+for your particular system (including paths), so it's not really meant to
+be installed or redistributed at the moment.
+
 If you exit the interpreter you get a pygame window with all the flowgraphs
 plus a pdb prompt. Moving around in the resulting flow graph is difficult
 because of the sheer size of the result. For this reason, the debugger prompt