15,091
edits
Changes
From Gramps
m
→Run: insert programming joke here ( Why do programmers count from zero, when everyone else starts at 1? )
=== Run ===
==== Option 01: run from source repo ====
From Gramps 4.2.x and master in the top-level directory you only need to type (this assumes your default python is python3):
python Gramps.py
==== Option 12: run from source repo ====
For Gramps 4.1.x and earlier (You can use either python or python3 substitute as necessary ):
PYTHONPATH=/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python Gramps.py
==== Option 23: use the build code ====
Here, we use the code build in <code>trunk/build</code> directory to run Gramps. For compiled programs this is the only way, but for Gramps nothing is compiled. It is not bad however to keep your code separated from your execution, as deleting the build directory is easy. After a code change in your source, you then need to run however <code>python setup.py</code> again to update the build direcotry. To run Gramps from build, do
cd trunk/build/lib.linux-$(uname -m)-2.7/
