Building on Linux

Building Guide

Introduction Getting the source Basic Concepts Build Requirements Building on Windows Building on Mac OS X Building on Linux Building on Solaris

Requirements

Hardware Requirements

• 1 or more reasonable fast CPUs, x-way CPU's recommended.

• 1 GB Ram ( 2 GB recommended )

• 10 GB free disk space

Software Requirements

• glibc:
  • for OOo<=3.1: 2.2.x or higher
  • for OOo>3.1: 2.3.2 or higher

• C/C++ Compiler
  • gcc >= 3.3
  • current reference compiler gcc 4.2.3

• The X11 development libraries and header files¹.

• PAM including the development headers².

• bash³.

• The gpc general polygon clipper library release 2.31, located at http://www.cs.man.ac.uk/aig/staff/alan/software/. Download and unpack the tarball. You should have the files gpc.c and gpc.h in $SRC_ROOT/external/gpc.

• gtk2 and libtiff including the development headers⁴.

Full Builds

To perform a full build, you need to follow these steps:

configure

• Run the configure script to check all requirements. Run the following command to view all possible options.

./configure --help

An example configure command (on Ubuntu 9.04 with as much libraries by the system used as possible):

./configure --with-use-shell=bash --with-system-libs \
--without-system-jars --without-system-icu --without-system-agg \
--without-system-lpsolve --without-system-mspack --disable-mozilla

See the last information box in the configure script for more information for your platform.

Please check for any warnings emitted by the configure-script.

bootstrap

When configure finished successfully, run:

./bootstrap

to create the dmake executable required to build OpenOffice.org.

setting the enviroment

When the configure script has been run successfully a file LinuxIntelEnv.Set.sh was created⁵. Do this:

source LinuxX86Env.Set.sh

to set up the enviroment for the build.

configure to build a ready-to-run installation (optional)

To have the build create a ready-to-be-run installation for testing purposes, set the following environment variables⁶.

export LOCALINSTALLDIR="/my/Destination/Dir"
export PKGFORMAT="installed"

If you do not set PKGFORMAT, native packages (.deb/.rpm) will be build.

starting the build

Build the software by typing the following in $SRC_ROOT⁷:

dmake

The building procedure will take at least an hour (on a 3 GHz Quad-Core with 8GB RAM).

Partial Builds

There are two ways to do partial builds:

• compatible
• incompatible

Only do compatible partial builds if you know exactly what you are doing. Template:Documentation/Note

rebuilding from a module (incompatible build)

If you decide to rebuild a module in an incompatible way, you will need to rebuild all modules depending on it (directly or indirectly)

cd $SRC_ROOT/instsetoo_native
build --from $INCOMPATIPLEMODULE --prepare
build --from $INCOMPATIBLEMODULE

rebuilding a module (compatible build)

To rebuild a module you can delete all output directories with, rebuild and redeliver into the solver with:

cd $MODULE
build --from $MODULE --prepare
build && deliver

A simple build in $SRC_ROOT/instsetoo_native will recreate the installation sets, provided all other modules have already been build.⁸

This does not check for incompatible modules. If unsure, use an incompatible build (see above).

Building a module with Debug Information

To rebuild a module with debug information and additional assertions and checks, run:

cd $MODULE
build --from $MODULE --prepare # removes old output trees and solver
build --from $MODULE

Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.

Finding Installation Sets

The english installation set will be located at $SRC_ROOT/instsetoo_native/unxlngi6.pro/OpenOffice/{deb,rpm,archive}/install/en-US/⁹.

See Also

• Building OpenOffice.org (esp. the Tips and Tricks section for stuff like ccache)

Footnotes

¹Template:Documentation/Note

²Template:Documentation/Note

³Template:Documentation/Note

⁴Template:Documentation/Note

⁵Template:Documentation/Note

⁶Template:Documentation/Tip

⁷Template:Documentation/Note

⁸

build --all would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use build --from --prepare.

⁹The en-US in the path names indicates that the localization is American English. This value corresponds to the language tags defined by RFC 1766 (Tags for the Identification of Languages). The German installation set will be located in a de subdirectory. This scheme holds true for all localizations you may have chosen explicitly.

Note that you can only build the language packs after you have build the complete office with all selected languages.

Content on this page is licensed under the Public Documentation License (PDL).