Revision as of 06:25, 12 August 2006

PPC Macs

gnucash-1.8

Fink is a package-management tool making it easier to install all your favorite *nix tools and libraries under OS X. It's also the easiest way to run gnucash-1.8 under Mac OS X; in general (Intel Mac users see below), gnucash-1.8 installation is as simple as:

1. download and install fink
2. run 'sudo apt-get install gnucash'
3. start up X11 and run 'gnucash &' from an xterm

Once a gnucash-2.0 package is available for fink, the process for gnucash-2.0 will be similar although you may need to enable the unstable tree first. At this time, however, it is not yet available in fink and requires a bit more effort on the part of the installer. If running prerelease software for your financial data, downloading and compiling from source, or making minor tweaks to software configuration files by hand makes you uneasy, you might want to stick with 1.8 until 2.0 is available as a fink package. If not, read on.

gnucash-2.0

It is quite possible to run gnucash-1.9.5+ from svn on Mac OS X. This is how I accomplished it (with a bit of help, of course).

Dependencies and Fink

Gnucash has a significant number of dependencies. Although it should be entirely possible to install them manually, it's much easier to use fink.

Installing dependencies

Note: you probably do need the unstable tree turned on in fink to get some of these packages.

David Reiser advised me to start with the following fink packages to get my dependencies straightened out:

gconf2, gconf2-dev, gconf2-shlibs
glib2, glib2-dev, glib2-shlibs
gtk+2, gtk+2-dev, gtk+2-shlibs
guile16, guile16-dev, guile16-libs, guile16-shlibs, guile16-gtk
slib, slib-gu16
libart2, libart2-shlibs
libglade2, libglade2-shlibs
libgnomeprint2.2, libgnomeprint2.2-dev, libgnomeprint2.2-shlibs
libgnomeui2, libgnomeui2-dev, libgnomeui2-shlibs
libgsf, libgsf-dev
gtkhtml3.8.15, gtkhtml3.8.15-dev, gtkhtml3.8.15-shlibs
libxml2, libxml2-bin, libxml2-shlibs
pango1-dev, pango1-xft2, pango1-xft2, pango1-xft2-shlibs
pango1-xft2-ft219, pango1-xft2-ft219-dev, pango1-xft2-ft219-shlibs
freetype219, freetype219-shlibs

You can probably do this in one fink command, although you may run into circular dependency issues and need to keep trying (fink won't try to reinstall packages that are already installed):

fink install gconf2 gconf2-dev gconf2-shlibs glib2 glib2-dev glib2-shlibs gtk+2 gtk+2-dev \
 gtk+2-shlibs guile16 guile16-dev guile16-libs guile16-shlibs guile16-gtk slib slib-gu16 libart2 \
 libart2-shlibs libglade2 libglade2-shlibs libgnomeprint2.2 libgnomeprint2.2-dev \
 libgnomeprint2.2-shlibs libgnomeui2 libgnomeui2-dev libgnomeui2-shlibs libgsf libgsf-dev \
 gtkhtml3.8.15 gtkhtml3.8.15-dev gtkhtml3.8.15-shlibs libxml2 libxml2-bin libxml2-shlibs pango1-dev \
 pango1-xft2 pango1-xft2 pango1-xft2-shlibs pango1-xft2-ft219 pango1-xft2-ft219-dev \
 pango1-xft2-ft219-shlibs freetype219 freetype219-shlibs

This will probably pull in other dependencies; although I had all but seven of the packages above installed, my fink command pulled in 58 additional packages and took roughly four hours to complete on a G4/800 with 1 GB of RAM.

g-wrap

This is where things start to get a little interesting. g-wrap 1.3.4-14 is the most recent version available via fink. g-wrap 1.3.4 is not compatible with aqbanking / ofxconnect, so if you need that functionality you are advised to download and install a more recent g-wrap yourself.

To further complicate matters, g-wrap 1.3.4 does not compile with gcc 4.0. There are two possible solutions to this problem. We can install g-wrap 1.9.6 manually and still use gcc 4.0 or we can choose to use gcc 3.3 and install g-wrap 1.3.4-14 using fink.

g-wrap 1.9.6 manually

Download and unpack the g-wrap 1.9.6 source code:

$ curl http://download.savannah.gnu.org/releases/g-wrap/g-wrap-1.9.6.tar.gz -o g-wrap-1.9.6.tar.gz
$ tar xfz g-wrap-1.9.6.tar.gz

Compile and install the source code:

$ cd g-wrap-1.9.6
$ ./configure
$ sudo make all install

If you have previously installed an earlier version of g-wrap using fink, you might need to remove it in order for the gnucash configure-script to find the correct version:

$ sudo fink remove g-wrap g-wrap-dev g-wrap-shlibs

g-wrap 1.3.4-14 using fink

2006-06-21: g-wrap-1.3.4-1014 compiles on Intel Mac Darwin 8.6.1 with gcc 4.0.1

We will compile both g-wrap and gnucash with gcc 3.3 (by changing the default compiler). Hopefully, this will be as simple as:

$ sudo gcc_select 3.3

(If this does not work, you probably don't have gcc 3.3 installed. I'm not sure whether XCode or fink is the appropriate place from which to get gcc 3.3, but I had it installed. Fink does have a gcc3.3 virtual package, and that may be a good place to start.)

Now, I was slightly concerned about whether or not g-wrap might try to interface with the wrong version of guile, so I decided to remove guile 1.4. This may or may not be necessary, but it can be achieved by:

$ sudo fink remove guile guile-dev guile-shlibs

2006-06-21: dpkg on Intel Mac Darwin 8.6.1 removes guile-dev automatically and replaces it with guile-dev16

As I didn't get any complaints from fink about dependency breakage, I'm guessing that I didn't really need guile 1.4 installed anyhow.

With those side excursions out of the way, go ahead and install g-wrap:

$ sudo fink install g-wrap g-wrap-dev g-wrap-shlibs

gnucash 1.9 / 2.0 from SVN

Get the source

Go to an appropriate directory and grab either a tarball from the website or just pull the latest source from Subversion svn. I did the latter, putting the gnucash tree under my 'src' directory in my Documents folder:

$ cd ~/Documents/src/
$ svn checkout http://svn.gnucash.org/repo/gnucash/trunk gnucash

(If you get 'svn: command not found', then you don't have Subversion installed; you can install it from fink with 'sudo fink install svn-client-ssl' or download and expand a tarball from the website. If ~/Documents/src does not exist, you can either 'mkdir ~/Documents/src' and then cd to it or you can use another location of your choosing, so long as you remember where it is.)

Remove gnucash-1.8

Unfortunately, it is necessary to remove gnucash-1.8 prior to compiling 1.9 or later versions. Assuming you used fink to install gnucash-1.8, you may uninstall it with:

$ sudo fink remove gnucash

If you have never installed 1.8, then you may skip this step. If you installed 1.8 via another method, you will have to uninstall it via another method.

Set environment variables

1. Change PATH environment variable so that the build sees fink's guile 1.6 binaries instead of others:

$ export PATH=/sw/share/guile/1.6/scripts/binoverride:$PATH

1. Set CFLAGS, CPPFLAGS, and LDFLAGS to make sure that the compile process includes fink-provided libraries:

$ export CFLAGS="-L/sw/lib -I/sw/include"
$ export CPPFLAGS="-L/sw/lib -I/sw/include"
$ export LDFLAGS="-L/sw/lib"

autogen, configure, make

First, change to the gnucash directory from where you either downloaded the svn tree or expanded the tarball.

$ cd gnucash

Feeling lucky? Run:

$ ./autogen.sh ; ./configure --with-g-wrap-prefix=/sw --enable-compile-warnings ; make ; sudo make install

Note that this will install in the usual /usr/local locations. If you'd prefer to install elsewhere, you may do so by using the --prefix switch; I did this because I wanted to keep the prerelease, non-fink built stuff in one place so that it would be easier to remove later when 2.0 becomes available through fink. I created a directory ~/usr and installed there with:

$ ./autogen.sh ; ./configure --with-g-wrap-prefix=/sw --enable-compile-warnings --prefix=~/usr ; make install

(sudo was not necessary for the make install step because I wasn't installing into a privileged directory)

If this doesn't work, you should probably try each step separately:

$ ./autogen.sh
$ ./configure --with-g-wrap-prefix=/sw --enable-compile-warnings --prefix=~/usr
$ make install

Caveats

1. This is pre-release software on a platform that is very similar yet significantly different from those use by most of the developers. Unexpected stuff is to be expected.
2. If you change your mind on where you want to install gnucash after the first time you run make, you may need to clean up and recompile to get things cleanly installed in the new location, i.e.:

make distclean ; ./autogen.sh ; \
 ./configure --with-g-wrap-prefix=/sw --enable-compile-warnings --prefix=~/other ; make install

1. Compiling may take a while, especially on older hardware, so you're advised to get the location right the first time. Trust me.

Easier with new Fink 0.8.1 - Works with 2.0.0

Once you have upgraded to Fink 0.8.1 with the 10.4 native tree instead of the transitional one all of the gcc 3 vs 4 problems seem to have been resolved. I followed the instructions here for the most part to build 2.0.0 - but I just put g-wrap g-wrap-dev g-wrap-shlibs into the big fink install line, accepted all of the defaults for the questions that it raised along the way, and it works perfectly.

I have a PowerBook G4 so this has no bearing on the Intel Mac problems.

Intel Macs

gnucash-1.8

As of June, 2006, GnuCash-1.8 does not work on Intel-based Macs. Both 1.8.x and 1.9.x series installations have dependencies (such as libgnomecanvas Gnome Bug #339489) which are known not to function correctly in this environment. As the known issues reside in external libraries (i.e. not within the GnuCash source tree), we are hoping that they will be resolved by the maintainers of those libraries (or their fink ports). Please check the gnucash (-users and -devel) and fink-users mailing list archives for more history and updates.

gnucash-2.0

As of August 2006, Gnucash 2 works fine on Intel Macs. Installation instructions for gnucash-2.0 on Intel Macs may be found here.

Final Words

Currently, none of the primary GnuCash development occurs under OS X; as such, clear and specific bug reports (particularly of new issues not already reported) may be helpful. If you encounter problems, please check the mailing list archives first and then, if your problem cannot be resolved based on the information found there, report it to the mailing list. Please do remember that GnuCash developers are volunteers and are not responsible for your computer; as such, your help (in the form of exhausting readily available resources before asking for help and in asking for help in a clear manner) is appreciated.