openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Richards <>
Subject Re: Who wants to build OpenOffice?
Date Mon, 05 Sep 2011 22:34:36 GMT
My build machine runs Ubuntu 11.04 (Natty) with a 64 bit kernel.

To get the deps needed to build OOo, I used apt-get build-dep on LibreOffice
package (as this is what Ubuntu is packaged with at this time) I figured
they're still fairly similar.
I did need to install the ccache package separately.

I passed configure nothing special (followed the wiki's directions).

Below is roughly what I did to get it building, (I am going from memory
here. Dug around my command history to see what I did).

svn co ... path/to/source

cd path/to/source
mkdir  /path/to/ccache/dir
source ./
export CCACHE_DIR="/path/to/ccache/dir"
ccache -M 2G -F 100000
export CXX="ccache g++"
export CC="ccache gcc"
build -P8 --all (my build box is a Quad Core, with 6 GB Ram)

About an hour later, maybe two. I followed the wiki's instructions to
confirm my build worked (didn't do a whole lot of testing), and it did.
These are more some notes, needs some polish before it ends up as
anything official in my opinion.

On Mon, Sep 5, 2011 at 4:51 PM, Rob Weir <> wrote:

> On Mon, Sep 5, 2011 at 4:48 PM, Matt Richards <> wrote:
> > Now that I've built OpenOffice on Linux with moderate success, I'd like
> to
> > lend a helping hand with the documentation side of things. As far as I am
> > aware, the existing (maybe old now) wiki has been migrated to Apache
> Infra
> > (via VM). Does this content need to be moved to the confluence wikis
> > eventually? I do apologies if this is off topic, there's been so much
> > discussion going on proving difficult to follow everything all the way
> > through.
> >
> Excellent.  What distro where you using?  And what configure flags?
> For the sake of this exercise we should probably track, on a wiki page
> (confluence community wiki is fine) what combinations we're trying and
> what corrections we'll want to make in the build instructions.
> It is not clear yet where the build instructions will finally end up
> living, but we don't need to solve that problem quite yet.
> -Rob


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message