Difference between revisions of "Ubuntu Build Instructions"

From Apache OpenOffice Wiki
Jump to: navigation, search
(major additions)
m
Line 16: Line 16:
 
*ubuntu-dictionary.diff
 
*ubuntu-dictionary.diff
 
*fontconfig-substitute.diff
 
*fontconfig-substitute.diff
 +
 +
You can try to comment them out in the <code>apply</code> file, but this may have unexpected effects later on in the build...
  
 
===Tips===
 
===Tips===
A shell script like the one below will alert your attention upon completion of the quite lengthy build process.  Run it after <code>./download</code> completes.
+
A shell script like the one below will alert your attention upon completion of the quite lengthy build process.  Run it after <code>./download</code> completes in place of <code>make</code>.
 
<code>
 
<code>
 
   #!/bin/bash
 
   #!/bin/bash
Line 32: Line 34:
  
 
===See also===
 
===See also===
*[[Debug_Build_Problems]]
+
*[[Debug Build Problems]]
  
  
 
[[Category: Distribution-Specific Build Instructions]]
 
[[Category: Distribution-Specific Build Instructions]]

Revision as of 08:04, 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

As of 5/24/2006, the following patches listed in ooo-build/patches/apply do not apply successfully:

  • disable-helpcontent2.diff
  • ubuntu-lpi.diff
  • ubuntu-dictionary.diff
  • fontconfig-substitute.diff

You can try to comment them out in the apply file, but this may have unexpected effects later on in the build...

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.

See also

Personal tools