[[CategoryFile:Developers/Packagingmacos_200x200.png|128px|right|link=Download#Mac_OS_X]]Installation of the ready-to-run Gramps application for Mac OS X. This is also known as the GTK-OSX port of Gramps for Mac. It is a single, stand-alone bundle which uses the native quartz windowing system of Mac OS X instead of X11.

The GTK-OSX port of GRAMPS for '''MacOS versions''' Gramps 5.0 requires Mac is expected to supersede the Macports OS X 10.9 (Mavericks) and Fink versionslater. Gramps 5. It is closer to a native 1 requires at least Mac application and should rely less on other programs, so should be easier to use and maintainOS X 10.10 (Yosemite).

Mac GRAMPS is available for both Intel and PPC Macs;'''Back up your databases:''': If you're using Time Machine, that's already taken care of. The distribution page carries both a binary application that should work as soon as (You do test your Time Machine backups periodically, right?) But it is downloaded, and also doesn't hurt to have a build environment which should allow spare copy set aside before starting up a Mac with new version. If you've been using the Apple Xcode tools to Gtk-OSX build the whole thing from scratch, version 3. The binary application was built for OS X 102.54 or later, just copy <code>Library/Application Support/gramps/grampsdb</code>.7 but should (in theory) work on OS X 10.4. To discover what OS Right click/option click and processor is in select "Make a Mac, choose About This Mac copy" from the Apple menu in the top left of the Desktop screen. It will be named <code>grampsdb(2)</code>.

== How ;'''New Version Notice:''': If you are upgrading from the pre-built Gramps Application version 3.2.3 or earlier (or a build from source version) and you want to Download keep your old database and settings, you'll need to create a <code>Library/Application Support/gramps</code> folder with your existing data in it. Unless you've changed the location in Preferences, the data is in a hidden folder in your home directory called "<code>.gramps</code>". Select a Finder window and run select Go>Go to Folder from the binary GRAMPS application menu. Type "<code>/Users/yourname/.gramps</code>" in the dialog box that opens up, and click on "Go". (Yes, substitute your userid for Mac =="yourname".) The hidden folder will appear, highlighted and open. Option-drag the whole thing to <code>Library/Application Support</code> (the one in your home folder, not the one in your boot drive's "root" directory). Slow-double-click on the new copy so that you can edit the name and delete the '.' at the beginning to unhide it.

If there is {{man note|''Migrating to [https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon Apple Silicon]?''|Make an existing GRAMPS database, it is wise to create a XML backup archive of an existing GRAMPS database before trying a new program, as described in the note your databases on backups below. GRAMPS for your Intel Mac and copy them to your Apple Silicon Mac is still new and untestedrestore them there after installing Gramps. There seems to be a binary object incompatibility in SQLite3 databases, even when running an Intel binary using Rosetta2. Take care!}}

Any browser on From the Mac will '''[[Download#Mac_OS_X]]''' page download the binary application, and depending on how dmg. Once it's configureddownloaded, uncompress you can open the file (just double click on it and store it, usually in the Downloads stack. If it Finder if your browser doesn't uncompress (open it's still called .zip instead of GRAMPS with a pretty family tree iconautomatically) then double-clicking it should turn it into GRAMPSand drag the Gramps application wherever you like. It can be dragged to the Desktop for convenienceOnce installed on your computer, or stored in the Applications folderit opens like any other application.

'''Links with other programs:''' Double-clicking on an image in the GRAMPS application media reference editor should launch GRAMPSbring up Apple Preview (or a whatever program you've set as the default to edit that kind of image) to view the image. Clicking the view button in an internet reference should bring up the URL in the default browser. It Should Just WorkClicking the Google Maps button in the Places display should bring up the map in the browser.

The GRAMPS application takes its working language from Gramps doesn't use the System Preferences - International settings for the DesktopX11 Mac package. It's useful to install [http://www. If the list of desired languages there shows Esperanto - Russian - French - English then GRAMPS should work in Esperantodocumentfoundation. If that translation isn't available for a particular phraseorg/download/ LibreOffice], it should produce Russian[http://www.calligra-suite. If that's not available for a particular phrase org/ Calligra] (in the place completion toolor [http://www.neooffice.org/ NeoOffice], for examplea more mac-friendly version) then GRAMPS should produce French, and then eventually Englishto work on your reports after saving them from Gramps.

Double clicking an image '''File structure:''' Gramps database and settings files can be found at the following places in the media reference editor should bring up Apple Preview, or a similar program, to view the imageMac file system (Gramps Version 3.2. Clicking 5 and later):* The Gramps database with the view button in an internet reference should bring user's genealogical information is stored under <code>/Users/<username>/Library/Application Support/gramps/grampsdb</code>* Setting files (ini-files) are found here: <code>/Users/<username>/Library/Application Support/gramps/gramps51</code>* Start-up settings for Gramps (for e. g. the URL environment variable LANG) can be accessed through Gramps.app (generally in the default browser/Applications): Right click on "Gramps. Clicking app", select "Show Package Content" from the Google Maps button in menu, the Places display should bring start-up the map settings are found in the browserfile <code>Contents/MacOS/Gramps</code>.

The first binary GRAMPS is built from gramps-3.1.2. If this reads an existing database from an earlier version of GRAMPS (like Macports) it will demand you want to do a database conversion, and there is no way to reverse this step. It is thus good practice when installing this binary GRAMPS on a run Gramps with different locale settings than you use for your system with an existing gramps databasesettings, first, to you can use Apple Time Machine to create backups, and second, to set aside a specific backup of an old GRAMPS database in case anything goes badly wrong. Unfortunately, the GRAMPS database is in a hidden directory which Finder doesn't show"defaults" program from Terminal. One way to fix this is to create a link to the database in a non-hidden file. To do this, open a unix terminal with Finder-app (Applications-:Utilities-:Terminal, and at the prompt there type ln -s .gramps gramps_user_directorywhich should create a directory, gramps_user_directory, showing the GRAMPS database in Finder. (That's dot-gramps in that command!app) Hitting Copy then Paste on this directory in finder will '''''not''''' create an explicit backup, it will only create a second link pointing at the original GRAMPS data! Instead, you can type: cp defaults write -r .gramps gramps_backupapp Gramps AppleLocale "de_DE"It is ''unfortunate'' that the current Macports GRAMPS crashes if it is used to produce a backup archiveset Gramps to operate in German with German calendar and formatting.

Known bugs The settings are stored in the application are described at [[Mac gtk~/Library/Preferences/org.gramps-osx port bugs]] and it is a good idea to look there for workaraoundsproject.gramps. In particular, Macs with a dialect of English (like British English) as their first choice language need a tweak to keep Gramps talking English!plist

GRAMPS stores all Note that you will need to run Gramps at least once before the defaults system will recognize its internal data in ~/gramps_user_directory. So, existence; before that trying to upgrade a binary GRAMPS application to a newer version, just throw the old application in the Trash. Everything in ~/gramps_user_directory use defaults will still be produce an error about therebeing no Gramps application. Download [[Howto:Change the new version language of the application and just use it. It will use all the old data still stored reports]] has more information on language features in ~/gramps_user_directoryGramps. If you don't like the new version and want the old one backWhen reading it, throw remember that AppleLanguages (which corresponds to the new version in language list on the Trash and fetch the old one back from the Trash. GRAMPS binary applications are labeled with a version string, -macnn, which can be seen by selecting Languages & Text system preference pane) sets the application package LANGUAGE environment variable and choosing Get Info from AppleLocale (Formats in the context (right-clickLanguages & Test pane) menusets the LANG variable.

== How the Apple binary application works = Dictionaries ===The spelling checker uses [https://en.wikipedia.org/wiki/MySpell MySpell] dictionaries -- the same ones that [http://www.documentfoundation.org/download/ LibreOffice] and NeoOffice use. Unfortunately, they bury them in their application called GRAMPS on the desktop is actually a complete directory hierarchy called grampsbundles, so you can download them [http://archive.services.openoffice.org/pub/mirror/OpenOffice.org/contrib/dictionaries/ here].app stored You need to install them in the directory ~/DesktopLibrary/Dictionaries, where ~ is the home directory of the logged-in userand you'll need to authenticate as an administrator to do so. The contents If you have one of them installed and know how to make symbolic links from the application directory hierarchy can be seen command line, you'll find them in finder by selecting the application and choosing Show Package Contents from /share/uno_packages/cache/uno_packages, scattered about in the context (righthash-click) menunamed directories. Using cd You'll need to link both the aff and ls in a shell at a unix terminaldic files (e.g., the "hidden" contents of the package are actually always visible en_US.aff and not hidden at allen_US.dic).

The binary GRAMPS application contains not only the GRAMPS Python sources and all their internationalised translations, but also a complete Python 2.6.2 interpreter, and the Python code libraries distributed with that, and the compiled C libraries for graphics features like gtk, glade and pango. These are all fixed for a particular version of the distributed binary application. The only way === If something seems to change them is to download a new distributed binary GRAMPS application. This is intended to fix a major issue with earlier GRAMPS Mac implementations, where the program depended on so many different distributions that were always changing that determining what change introduced what bug was very hard.go wrong ===

One downside of the way that Mac packages work is that, to achieve a reasonable download size, some libraries and programs are missed out of the packaged application. This can cause GRAMPS crashes, or sometimes just cause some program features to be missing. Crashes of the packaged application usually produce You'll find error messages on in the consolelog, which you can be seen (even after the crash has finished) by choosing Finder-view with <code>/Applications-/Utilities-/Console. There is a delay of perhaps up to a minute between the crash occurring and the messages appearing on the console.app</code>

A simpler way to see messages from GRAMPS, should any appear, is to start it from a unix terminal. To do this, open a terminal with Finder-Applications-Utilities-Terminal, All of the known bugs in previous version have been corrected in Gramps {{Version_Mac}} and type (for a GRAMPS application on the Desktop) cd / ; ~/Desktop/grampslater.app/Contents/MacOS/grampsand that should run GRAMPS and produce any messages with There will no delay. The file ~doubt be new ones; report them in the usual way on [https:/Desktop/grampswww.app/Contents/MacOS/gramps is a shell script, as is ~/Desktop/gramps.app/Contents/MacOS/gramps-bin which it callsproject. gramps-bin calls the Python 2.6.2 interpreter ~org/Desktopbugs/grampsmy_view_page.app/Contents/MacOS/python to run php Mantis] ([[Using the GRAMPS code which is stored in ~/Desktop/gramps.app/Contents/Resources/share/grampsbug tracker]] instructions). Local translations are stored in ~/Desktop/gramps.app/Contents/Resources/share/locale. Standard python code When reporting what you're sure is in ~/Desktop/gramps.app/Contents/Resources/lib/python2.6an OSX specific bug, and please set the compiled C libraries are in ~/Desktop/gramps.app/Contents/Resources/lib/*.dylib. Only the GRAMPS Python source is shipped in the binary application. If other sources are neededPlatform field to "mac" (no quotes, caps, the GRAMPS build environment must be usedor spaces!) so that I can find it easily.

Should GRAMPS produce a message indicating that it crashed because it could not find a particular library or source filePrevious Gramps version 3.2.4, then do please post a message on the GRAMPS users or developers mailing list, or post a bug. These tedious issues bugs are usually easy to fix. Packaging GRAMPS like this (as opposed to including everything and the kitchen sink) reduces the download size by more than a factor of threedescribed at [[Mac OS X:Build from source:gtk-osx:bugs]].

==Building GRAMPS Gramps stores all its internal data in <code>~/Library/Application Support</code>. So, to upgrade a Gramps application bundle to a newer version, just throw the old application in the Trash. Make a backup copy of your data, just in case, then download the new version of the application and just use it. If you don't like the new version and want the old one back, throw the new version in the Trash and fetch the old one back from Scratch==the Trash. The Gramps version is shown in Finder if you use column view; otherwise right click on it and select Get Info.

Building GRAMPS from scratch is useful to produce a version not currently available as a binary (for example, a PPC version) or to produce a complete environment for debugging and further development, including debugging of all the C libraries GRAMPS uses, like gtk. To build GRAMPS from scratch, click on an entry from the [http[Category:Developers//www.gramps-project.org/apple/ download pagePackaging]] like gramps-3.1.2-mac13-builder.zip. The builder files are build environments. The downloaded builder file when uncompressed will produce a directory called gramps_important_info. This is intended to be saved at ~/gramps_important_info, where ~ is the home directory of the logged-in user. It's possible to download the builder file with any browser and to uncompress it and move it to ~/ and then to execute ~/gramps_important_info/build_gramps (by double-clicking it) entirely from within Finder. build_gramps should download a bunch of stuff (It may hang up if any of the required webservers are down) and build it. build_gramps does everything needed to build GRAMPS (provided Apple Xcode tools are installed). build_gramps uses the [http[Category://library.gnome.org/devel/jhbuild/unstable/ jhbuildDocumentation]] system to fetch code and compile it. It's important that jhbuild is not confused by any existing Macports or Fink installation. For this reason, it can be convenient to create a new Mac User account, without admin privilege, and log in to that account to fetch and run build_gramps. Admin access is not required to build GRAMPS from scratch: no sudo. jhbuild is installed in ~/Source, and produces a binary which appears in ~/bin. jhbuild then puts everything it is building in ~/gtk (controlled by the .jhbuildrc hidden file). ~/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. jhbuild gets its instructions on how to build things from the file ~/gramps_important_info/gramps.modules. This large file includes all the instructions to build all the libraries as well as GRAMPS itself, to avoid relying on jhbuild's own instructions, which might change with time and change a build of GRAMPS unexpectedly. The intent is that each major release of GRAMPS ported to Mac will see this gramps.modules file revisited to update build instructions for libraries to the latest stable releases. The application ~gtk/inst/bin/gramps can run GRAMPS straight from the build directory without any OS X packaging, provided that PATH searches ~gtk/inst/bin first to pick up the right Python. GRAMPS will not work, in this build, with the standard Apple 2.5.1 Python. jhbuild constructs a 2.6.2 Python for GRAMPS to use. build_gramps goes on to produce an application package on the desktop. It does this just by copying the relevant files, and creating some symbolic links in the target. The files come either from ~/gtk/inst, or from ~/gramps_important_info. It's a fairly ad hoc procedure. It's possible some critical Python file or compiled C library is missed out of the application and will only be discovered later. This is to reduce the download size. Finally, build_gramps creates a pair of zipped files, the zipped packaged application for download, and the zipped gramps_important_info directory for building. The version macnn which is given to the files (and to the file info for the packaged application) is taken from the file ~/gramps_important_info/built_version. To create a different built version (version 0 for testing, perhaps) invoke build_gramps from a command line with a single argument:* build_gramps 0 Good Luck!