gnucash versions 2.2 and 2.3 on same PC?

[Colin Law]

2009/7/15 Stephen R. Besch <sbesch at buffalo.edu>:
>...
>
> Source compilation is not really that bad. It's just that there tends to be
> a few things that don't get mentioned. For my money, I would recommend
> checking out the sources from svn. You will have to have svn installed
> already to do this:
>
>           sudo apt-get install subversion
>
> Then you can checkout the sources. First change to a suitable directory. I
> use something like ~/source_installs/gnucash.  Then enter:
>
>           svn co  http://svn.gnucash.org/repo/gnucash/trunk
>
> This will download the entire source package. What you need to know is that
> a lot of the files needed to make the project are not part of the base
> download - they are generated on your machine after you have the sources
> loaded. Largely this is to avoid the problem of widely varying
> hardware/software configurations by having the files generated on your
> machine.  First you need to execute autogen.sh. Change to the trunk
> directory and enter:
>
>       ./autogen.sh
>
> (If I recall, autogen.sh already has the executable bit set. If it doesn't,
> the above will fail and you will need to "chmod 775 autogen.sh" first!)
>  This will generate a whole bunch of files needed for the next (configure)
> step. Before configuring, it is almost always a good idea to write your own
> custom shell script that enters all the configuration parameters for you -
> it gets very tedious otherwise. Here's mine:
>
>       #!/bin/bash
>       ./configure -C --enable-debug --enable-ofx --enable-aqbanking
> --enable-compile-warnings
>
> Save it as something like "myconfig.sh". The -C is useful when configuring
> the first time, since it will cache the results and skip over the successful
> parts when you have to configure again after resolving any errors that
> configure detects. You should remove it after you get gnucash built the
> first time, since it can cause problems later by remembering things that it
> should not. You probably won't want the --enable-debug option (unless you
> are planning to run GC under the debugger). I left it there in case you need
> it later. It will make GC larger and load slower, so you should probably
> delete it. The other 3 options should be left as they are. Also, given that
> you are planning to run 2 versions, you almost certainly will want to add
> the --prefix option as indicated elsewhere on this thread. When you are
> ready, set the executable bit on myconfig.sh (chmod 775 myconfig.sh) and
> enter:
>
>      ./myconfig.sh
>
> This is unarguably the hardest part of the entire process. Unless you are
> extremely lucky, there will be lots of things missing and configure should
> tell you about all of them. Usually you can tell right away what is missing
> from the error messages. You'll have to fish around in synaptic for the
> needed packages. Most of these will be the "-dev" component of some library
> that you already have installed. You'll just need to be a bit creative in
> finding them since the exact package name is usually not given in the error
> message. Googling the error message text usually works, and this usually
> will save the day. The only real clunker (on Ubuntu at least) is the guile
> and slib stuff. See the link here for some help on this if you need it
> (http://wiki.gnucash.org/wiki/Building#slib_Issues).
>
> Once you get configure to complete without errors, the rest is simple:
>
>   make
>   sudo make install
>
> These will take a while, but when they are done, you should be able to run
> GC from the prefix directory. Later on, when you want to update to the next
> release of the trunk code, just type:
>
>   sudo make uninstall
>   svn update
>   ./myconfig.sh
>   make
>   sudo make install
>
> The 'sudo make uninstall' is probably not needed except on those rare
> occasions when one of the installed components will break the current
> version. I do it for insurance rather than suffer the irritation of tracking
> down the rare case when it is needed. Every once in a while you may also
> need to  ./autogen.sh first, but this should be really rare. Only do this if
> the new version won't work after doing all the above.
>
> Hope this helps..
>

I am sure it certainly will help, many thanks

Colin