Thanks that makes sense.
For me, I made sure to add it to my notes. To avoid confusion for
others, it may be good to either add this info on the website right
after the building from source, or adding a Makefile target named
"tarball" or something.
Cheers,
Davide Del Vento,
NCAR Computational & Information Services Laboratory
Consulting Services Software Engineer
On 06/20/2013 02:17 PM, Amaury Forgeot d'Arc wrote:
Hi,
2013/6/20 Davide Del Vento <ddve...@ucar.edu <mailto:ddve...@ucar.edu>>
Folks,
I've successfully translated pypy 2.0.2 as described here:
http://pypy.org/download.html#__building-from-source
<http://pypy.org/download.html#building-from-source> (which is
slightly different from running make).
Now I want to install it in a global location for others to use
(it's on a machine shared by many users). The problem is, I've done
this before, but I don't remember what I did and I did not write in
my notes about translating.
Do I just rename pypy-c to pypy, place it in a bin directory
somewhere in the PATH and do the same with site-packages and
PYTHONPATH (and corresponding actions to include, lib_pypy and
lib-python directories)?
Is there any reason why the makefile does not have an install
target, possibly with prefix option (other than lack of interest or
time to write it)?
The makefile is only to build the C binary. It is generated, by the way.
To build a pypy distribution, after translation you can call
pypy/tool/release/package.py; this is how the nightly downloads are made.
PyPy does not use any prefix or anything: to install, just unpack the
.tgz somewhere and eventually add a link in /usr/local/bin:
http://doc.pypy.org/en/latest/getting-started.html#installing-pypy
--
Amaury Forgeot d'Arc
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
