Changes

From Gramps

Running a development version of Gramps

2,610 bytes added, 22:57, 7 November 2013
Add gramps40 section from a merge of couple of other pages
The following describes one possible scenario for building and running the latest development version of GRAMPS on [http://en.wikipedia.org/wiki/Ubuntu_%28operating_system%29 Ubuntu]:== Preparation ==
{{man warn|1=Note|2=It * Install a recent version of Ubuntu, or Mint, which is beyond the scope of Ubuntu based. ''The steps in this documenthave been tested with Ubuntu 7.04, but [http://en7.wikipedia10, 8.org/wiki/VirtualBox VirtualBox] and [http://en04, 10.wikipedia04, 10.org/wiki/VMware VMWare] provide a great 10 and relatively easy solution to getting a clean build environment up 12.10, and running within 30 minutes on Linux.}}Mint 14''
[[File:Paralle_versions_in_VB.png|350px|right|thumb|Example on VirtualBox]]This picture shows * Install a parallel installation text editor if you plan on modifying the same machine of both the svn version (running on a virtual machine) and the latest stable versionGramps source. On the left hand side you You can see Gramps 3.3.0use any text editor such as gedit, kate, or sourcenav (<tt>sudo apt-0 SVN 16310 running with Python 2.7.1get install sourcenav</tt>), erik4, SPE, BSDDB 4or [http://www.8eclipse.4 and Linux kernel 2org Eclipse] with the python plugin.6.37 Instructions on Ubuntu Natty 11.04 alfa; on the right hand side you can see Gramps 3.2.5-1 with Python 2.6.6, BSDDB 4.7.3 [[Development using Eclipse and Linux kernel 2.6.35. The svn version is installed locally Pydev|installing and running in a virtual machine on Oracle VM 4configuring Eclipse for Gramps development]].0.0 r69151. The svn version was installed locally on Note the user home directory. Running the autogen script with --prefix=/home/user without make nor make install. I only ran the ''msgfmt'' to get the Dutch translation and copied the ''gramps.mo'' file to ''../trunk/po/local/LC_MESSAGES/'' and ran [[Programming Guidelines|programming guidelines for Gramps with the ''GRAMPSI18N=~/trunk/po python gramps.py'' in dir ~/trunk/src]].
* [[Getting_started_with_Gramps_development#Get_the_source_tree|Get the latest version of Gramps]]
== Gramps 4.0 and the master branch ==
{{man warn|1=warning|2=Do not open your existing databases with the master branch, it might destroy your data, and will make it impossible to use the data in the stable version {{stable_branch}}. To try it out, export your database to a gramps xml file, eg <code>test_master.gramps</code>, create a new family tree in the master branch, and import this xml file.}}
For the internationalization code to work, you need to have the translation tools.
On Debian, just run (as root) - ('''Only if Debian installs Gramps 4.0+ as Gramps version!):
apt-get build-dep gramps
On Fedora 8 - 10 (Fedora is up to version 17 now so does this still apply?), you will need:
yum install intltool gnome-doc-utils gettext git-core rcs
=== Build ===
Now go into the top-level directory and type:
python setup.py build
{{man warn|1=Warning|2=Do not install the development version if you don't know how to version python modules. That is, do '''not''' type {{man label|sudo python setup.py install}}. }}
=== Run ===
==== Option 1: run from source repo ====
Here, we use the code in working directory to run Gramps. This means that compiled python files will be stored there. This is not ideal, but the easiest way to develop Gramps, as changes are immediately picked up by the code.
Copy the const.py file created in build to your source directory if you want to use your source directory to work with Gramps:
cp build/lib.linux-$(uname -m)-2.7/gramps/gen/const.py gramps/gen/const.py
python Gramps.py
''Note'': the <code>lib.linux-$(uname -m)-2.7</code> folder name vary depending on your system (i686 or x86_64).
That is it. If you installed some dependencies of Gramps in non-default positions, you need to indicate with PYTHONPATH where they can be found, and with LD_LIBRARY_PATH where link libraries can be found. Eg, if you install GTK and spell checking from source too, you will need something like:
PYTHONPATH=/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python Gramps.py
==== Option 2: 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/
python -c 'from gramps.grampsapp import main; main()'
Again, it might be needed to set with PYTHONPATH where dependencies can be found, and with LD_LIBRARY_PATH link libraries, see option 1.
If you point your PYTHONPATH to the build directory, you can actually run Gramps from a random directory. Like this:
cd
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/ python -c 'from gramps.grampsapp import main; main()'
So, more general:
cd
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/:/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python -c 'from gramps.grampsapp import main; main()'
If the build directory is in your PYTHONPATH, you can also just execute the grampsapp.py module. So this will work too:
cd ~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/gramps
PYTHONPATH=~/gramps-trunk/build/lib.linux-$(uname -m)-2.7/ python grampsapp.py
<br clearor again more generally PYTHONPATH="all" ~/gramps-trunk/>* Install a recent version of Ubuntu, or Mint, which is Ubuntu basedbuild/lib.linux-$(uname -m)-2. ''The steps in this document have been tested with Ubuntu 7/:/usr/local/lib/python2.04, 7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python grampsapp.10, 8.04, 10.04, 10.10 and 12.10, and Mint 14''py
* Install a text editor if you plan on modifying '''Note''': At the GRAMPS source. You can use any text editor such as gedittime of writing, kateonly the last, or sourcenav (<tt>sudo apt-get install sourcenav</tt>), erik4, SPEso using grampsapp.py works, as not all imports in Gramps have been converted to relative or [http://wwwabsolute imports.eclipse.org Eclipse] with the python plugin. Instructions on [[Development using Eclipse and Pydev|installing and configuring Eclipse for GRAMPS development]]. Note the [[Programming Guidelines|programming guidelines for GRAMPS]]This conversion will be finished by end of 2012 however.
* Install {{man note|1=Known Problems|2=Some problems are due to the tools we will needmigration from GTK2 to GTK3: sudo apt-get install build-essential gnome-common libglib2.0[[GEPS_029:_GTK3-dev subversion gettextGObject_introspection_Conversion#Problems|list of known problems]]}}
* Create a directory for the == Gramps source: cd ~ mkdir gramps cd gramps3.4 and before ==
* [[Getting_started_with_Gramps_development#Get_the_source_tree|Get Install the latest version of GRAMPS]]tools we will need: sudo apt-get install build-essential gnome-common libglib2.0-dev git-core gettext
=== Build ===* Get ready to build GRAMPSGramps: cd trunkThe old versions of Gramps use autotools, so you need to run:
./autogen.sh
 
* Build GRAMPS:
make
 
=== Run ===
* Run Gramps:
python src/gramps.py
At this point, any time you want to update to the latest version of Gramps, simply run:
cd ~/gramps/trunk svn updategit pull --rebase
python src/gramps.py
If some of the GRAMPS Gramps constants have changed and you obtain an error in const.py, rerun the commands <tt>autogen.sh</tt> and <tt>make</tt>.
[[Category:Developers/General]]
Retrieved from "https://ftp.gramps-project.org/wiki/index.php/Special:MobileDiff/47125"

Navigation menu