Test Documentation in Linux
Test Documentation in Linux
For our purposes, “Linux” means any system that’s not Windows or Mac OS X. GnuCash uses Yelp, the GNOME documentation browser, to display its help--both the User Manual and the Concepts Guide. This documentation gets installed in the standard GNOME help directory hierarchy. Although not tested, it's very likely that a cygwin environment on Windows or a fink/homebrew/macports environment on OS X can equally be configured to run these documentation tests. GnuCash as installed from the Windows Installer package or the OS X/Quarz dmg on the other hand can not.
Aside from the above limitations you can test the documentation changes with any installed gnucash, version 2.6 or higher. Of course if you have written context help for a feature that is not present in your installed version of gnucash, you won't be able to test the direct context help button for that feature. You will however still be able to open the new help or guide in general from your installed (2.6+) version of gnucash.
If you want to test the changes you just made to the documentation without interfering with the already-installed versions, you need to install a development version of GnuCash locally first.
To test the changes, (1) install the changed documentation locally, and (2) tell your (locally) installed (2.6+) version of gnucash where to find it.
If you don’t want to test interaction with GnuCash, see below for a way to do that.
Install Development GnuCash Locally
Remember this can be skipped if you prefer and have version 2.6+ of gnucash installed. It's only required to run context help tests.
Without any special configuration the default installation directory will be /usr/local/... on Linux based systems. This is usually not a good location during development (or documentation changing), because this would interfere with your stable, running system and that's generally not what you want on a modern system where installing software is usually done via a package manager. So for development purposes we need to tell the build system to use another final location. This is done by running configure with the --prefix option. The installation directory should meet the following requirements:
- it should be a writable location for the user that runs make install
- it should not be in the default paths /usr or /usr/local
Build and install GnuCash locally as per Building. Let's say you've installed GnuCash in
Install Updated Documentation Locally
Let's say you wish to build your modified documentation in
These are the commands for that:
$ cd /home/$USER/code/gnucash-docs $ ./autogen.sh # First time only, when building from repository copy $ ./configure --prefix=/home/$USER/code/gnucash-docs-install # Add any other needed options... $ make install
Tell Development GnuCash Where to Find Docs
$ GCASH=/home/$USER/code/gnucash-install # For convenience if you built gnucash yourself, otherwise: $ GCASH=/usr # For convenience if you use a default installed gnucash $ GCASHDOCS=/home/$USER/code/gnucash-docs-install # For convenience $ XDG_DATA_DIRS="$GCASHDOCS/share:$XDG_DATA_DIRS:/usr/local/share:/usr/share" $GCASH/bin/gnucash &
That last line, with XDG_DATA_DIRS, is the crux of it. That environment variable tells GnuCash, among other things, where to look for the documentation. In fact, it tells any tool which uses Yelp (and Yelp itself) where to look for documentation. For example, try the following:
$ XDG_DATA_DIRS="$GCASHDOCS/share:$XDG_DATA_DIRS" yelp ghelp:gnucash-help &
That should open up your development-version GnuCash docs without first starting GnuCash itself. Handy if you don’t need to test GnuCash along with the docs--i.e., if you’re just updating sections that are already in the docs.
Now you can update both your local GnuCash and GnuCash docs freely and test their interaction.