Building on Linux
Building Guide
|
Introduction Getting the source |
Contents
Overview
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
- gcc 4.2.3 is the current reference compiler
- The X11 development libraries and header files1.
- PAM including the development headers2.
- bash3.
- general polygon clipper library release 2.31
- gtk2 and libtiff including the development headers4.
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.
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 created5.
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 variables6.
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
7:
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 change 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.8
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 debug=true --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/
9.
See Also
- Building OpenOffice.org (esp. the Tips and Tricks section for stuff like ccache)
Footnotes
89The 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). |