Difference between revisions of "Ubuntu Build Instructions"
(added cvs instructions inline) |
|||
| Line 1: | Line 1: | ||
This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point. | This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point. | ||
| − | One may obtain <code>ooo-build</code> via CVS | + | ===Obtaining ooo-build=== |
| + | One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands: | ||
| + | <pre> | ||
| + | export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome' | ||
| + | cvs login | ||
| + | cvs -z3 checkout -P ooo-build | ||
| + | cvs upd -Pd -r ooo-build-2-0-2 | ||
| + | </pre> | ||
| + | You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]). | ||
===Additional Required Packages=== | ===Additional Required Packages=== | ||
Revision as of 08:23, 25 May 2006
This tutorial will assume a stock Ubuntu 5.10 (Breezy) system as a starting point.
Obtaining ooo-build
One may obtain the stable 2.0.2 version of ooo-build via CVS with the following commands:
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome' cvs login cvs -z3 checkout -P ooo-build cvs upd -Pd -r ooo-build-2-0-2
You should then enter the ooo-build directory and run ./autogen.sh --with-distro=Ubuntu. Most likely you'll also want to add the --disable-kde flag (unless you're using Kubuntu).
Additional Required Packages
Packages may be obtained as follows:
sudo apt-get install package_name [additional_package(s)]
- automake1.9
- libmono-dev
- [please help populate the rest of this list!]
Failed patches
Some of the patches listed in ooo-build/patches/src680/apply may not apply successfully. You can try to comment them out in the apply file, but this is an experimental solution...
Tips
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after ./download completes in place of make.
#!/bin/bash
echo "Starting 'make' wrapper..."
cd ~/ooo-build
make
echo "\n\nCompilation finished."
mplayer -really-quiet ~/Music/My_Music_File.mp3
Caveats
Don't do something silly like execute udatedb while make is in progress. This will result in locking the filesystem as read-only and cause the build to fail.
