Revision as of 07:46, 17 July 2009

Building Guide

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

Introduction

Template:Documentation/Linux

Template:Documentation/Tip

Template:Documentation/Note

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 (optinal)

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).

Rebuilding a module

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

cd $MODULE
rm -rf unxlngi6.pro
build && deliver

(The directory name might be slightly different: 64-bit Linux is unxlngx6.pro for example)

Partial rebuild

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

The build process started with build --all in $SRC_ROOT/instsetoo_native will create an installation set in English. A simple build in $SRC_ROOT/instsetoo_native will also create the installation sets, provided all other modules are already built⁸.

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

For details, see Debugging

Finding Installation Sets

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

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 (see Building Localized Versions of OpenOffice.org).

Template:Documentation/Tip

Template:Documentation/Note

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).

@@ Line 145: / Line 145: @@
 <span id="Foot3"><sup>3</sup>{{Template:Documentation/Note|You can also (still?) use tcsh instead of bash, but bash is installed almost everywhere anyway. It is possible to use bash or tcsh as shell. This is switched with the <CODE>--with-use-shell</CODE> configure switch.}}</span>
-<span id="Foot4"><sup>4</sup>{{Template:Documentation/Note|Unless you disable the crash-reporter when running <CODE>./configure</CODE>.}}
+<span id="Foot4"><sup>4</sup>{{Template:Documentation/Note|The gtk2, jpeg and tiff libraries are not required if you disable the crash-reporter when running <CODE>./configure</CODE>.}}
 </span>
 <span id="Foot5"><sup>5</sup>{{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <code>LinuxX86Env.Set</code> instead:<br>
 <pre> source LinuxX86Env.Set
-  rehash</pre><br>
+  rehash</pre>
 If you do not use tcsh, it is better to delete that file, as it will get in the way for tab-completion sooner or later.}}
 </span>
 <span id="Foot6"><sup>6</sup>{{Template:Documentation/Tip|Alternativly you can set:<br>
-<pre>export FORCE2ARCHIVE=true</pre><br>
+<pre>export FORCE2ARCHIVE=true</pre>
 This will create a tarball that can easily be unpacked and run anywhere.}}
 </span>
 <span id="Foot7"><sup>7</sup>{{Template:Documentation/Note|You can also run:<br>
-<pre>make</pre><br>
+<pre>make</pre>
 but GNU/make will just start dmake. You can also run the following in the <code>instetoo_native</code> module:<br>
-<pre>build --all</pre><br>
+<pre>build --all</pre>
 For details run:<br>
 <pre>build --help</pre>}}
 </span>
-<span id="Foot8"><sup>8</sup><code>build --all</code> would rebuild changed/missing files.
+<span id="Foot8"><sup>8</sup>{{Documentation/Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}
-{{Documentation/Caution| However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}
 </span>
@@ Line 175: / Line 174: @@
 {{Template:Documentation/Tip|Running the configure script with the --with-lang option will introduce the build of additional language resources. This switch accepts one or more RFC 1766 language tags as arguments. Check the value of the <code>completelangiso</code> macro in <code>$SRC_ROOT/solenv/inc/postset.mk</code> for all the currently supported language tags.<br>
 Example:<br>
-<pre>./configure --with-lang="de fr"</pre><br>
+<pre>./configure --with-lang="de fr"</pre>
 This enables the build of the localized German and French version. The environment variable <code>WITH_LANG</code> will then contain the language tags of the additional (en-US will always be build)
 languages.}}

Difference between revisions of "Documentation/Building Guide/Building on Linux"

Revision as of 07:46, 17 July 2009

Contents