Fix and improve Pyston instructions in Compiling for Linux, *BSD

- Fix SCons path to match Pyston 2.3.2's portable archive.
- Use a symbolic link instead of a wrapper script, which works the same.

(cherry picked from commit 1399f7bac3)
This commit is contained in:
Hugo Locurcio
2022-02-12 22:10:55 +01:00
committed by Rémi Verschelde
parent a3b6487ea2
commit 53c0fa893d

View File

@@ -242,14 +242,13 @@ to get even faster builds.
- Extract the portable ``.tar.gz`` to a set location, such as ``$HOME/.local/opt/pyston/`` (create folders as needed).
- Use ``cd`` to reach the extracted Pyston folder from a terminal,
then run ``./pyston -m pip install scons`` to install SCons within Pyston.
- Create a file with the following contents in ``$HOME/.local/bin/pyston-scons``::
- To make SCons via Pyston easier to run, create a symbolic link of its wrapper
script to a location in your ``PATH`` environment variable::
#!/bin/sh
ln -s ~/.local/opt/pyston/bin/scons ~/.local/bin/pyston-scons
$HOME/.local/opt/pyston/usr/bin/scons "$@"
- Instead of running ``scons <build arguments>``, run ``pyston-scons <build arguments>``
to compile Godot.
- Make the script executable: ``chmod +x $HOME/.local/bin/pyston-scons``
- Instead of running ``scons <build arguments>``, run ``pyston-scons <build arguments>`` to compile Godot.
If you can't run the ``pyston-scons`` script after saving it,
If you can't run ``pyston-scons`` after creating the symbolic link,
make sure ``$HOME/.local/bin/`` is part of your user's ``PATH`` environment variable.