Changes

From Gramps

Mac OS X:Build from source:Application package

177 bytes removed, 17:11, 20 October 2012
Building GRAMPS from Scratch: Update build instructions again.
jhbuild bootstrap
Now we need to build berkeleydb: jhbuild --moduleset=~/gramps-mac/gramps.modules build berkeleydbAnd rebuild python to include the bsddb module (it will notice that we have berkeleydb and do it automatically) jhbuild --moduleset=bootstrap.modules buildone --force pythonNow we're ready to build everything else: jhbuild --moduleset=~/gramps-mac/gramps.modules build meta-gtk-osx-bootstrap berkeleydb meta-gtk-osx-core meta-gtk-osx-python gramps
jhbuild by default puts everything it is building in ~/gtk (controlled by the hidden files ~/.jhbuildrc and ~/.jhbuildrc-custom ). ~/gtk/source contains the downloaded sources, and ~/gtk/inst contains the built libraries and applications. More is built than is needed in the final Gramps application - for example, the build tools are themselves built.
Once you've done this once, you can generally get away with just running
jhbuild --moduleset=~/gramps-mac/gramps.modules build meta-gtk-osx-bootstrap meta-gtk-osx-core berkeleydb python meta-gtk-osx-python gramps
to update everything that has been changed since the previous build. Most of the time nothing will have changed except gramps itself.
If you want to build the svn trunk, you should use the trunk setup files:
svn co https://gramps.svn.sourceforge.net/svnroot/gramps/trunk/mac gramps-mac-svn
and substitute " jhbuild --moduleset=~/gramps-svn" for "mac/gramps". If modules build meta-gtk-osx-bootstrap meta-gtk-osx-core berkeleydb4.8 python2.7 meta-gtk-osx-python gramps-svnShould you want to have both installed, you'll need to set up separate prefixes in .jhbuildrc-custom; gramps doesn't version its installations, so the most recent will overwrite the previous build.
== Gramps 3.3 and EXIF Editing ==

Navigation menu