Difference between revisions of "Ubuntu Build Instructions"
m |
(→Failed patches) |
||
| Line 11: | Line 11: | ||
===Failed patches=== | ===Failed patches=== | ||
| − | + | Some of the patches listed in <code>ooo-build/patches/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution... | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | You can try to comment them out in the <code>apply</code> file, but this | + | |
===Tips=== | ===Tips=== | ||
Revision as of 08:19, 24 May 2006
This tutorial will assume a stock Ubuntu 5.10 (Breezy) system as a starting point. One may obtain ooo-build via CVS according to instructions on the Getting It page. 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)]
- libmono-dev
- [please populate the rest of this list!]
Failed patches
Some of the patches listed in ooo-build/patches/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 run udatedb while make is in progress. This will result in locking the filesystem as read-only.
