Difference between revisions of "Documentation/Building Guide/Building on Linux"
B michaelsen (Talk | contribs) m (formatting) |
B michaelsen (Talk | contribs) m |
||
Line 19: | Line 19: | ||
= Introduction = | = Introduction = | ||
{{Template:Documentation/Linux| This document describes building OpenOffice.org on Linux.}} | {{Template:Documentation/Linux| This document describes building OpenOffice.org on Linux.}} | ||
+ | |||
+ | {{Template:Documentation/Tip|You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases.}} | ||
+ | |||
+ | {{Template:Documentation/Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}} | ||
= Requirements = | = Requirements = | ||
Line 48: | Line 52: | ||
* gtk2 and libtiff including the development headers<sup>[[#Foot4|4]]</sup>. | * gtk2 and libtiff including the development headers<sup>[[#Foot4|4]]</sup>. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Full Builds = | = Full Builds = |
Revision as of 07:33, 17 July 2009
Building Guide
|
Introduction Getting the source |
Contents
Introduction
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 files1.
- PAM including the development headers2.
- bash3.
- 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 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 (optinal)
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).
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 built8.
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/
9.
See Also
- Building OpenOffice.org (esp. the Tips and Tricks section for stuff like ccache)
- Compatible Builds
- Module Build Order
Footnotes
1Should be in place with most Linux distributions. Note the there are currently some issues with X version 4.3.
2PAM should be installed by default on most linux distributions. You should only need to add the development package.
3You 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 --with-use-shell
configure switch.
4Unless you disable the crash-reporter when running ./configure
.
5When you want to use tcsh instead of bash, you will need to use the file LinuxX86Env.Set
instead:
source LinuxX86Env.Set rehash
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.
6Alternativly you can set:
export FORCE2ARCHIVE=true
This will create a tarball that can easily be unpacked and run anywhere.
7You can also run:
make
but GNU/make will just start dmake.
You can also run the following in the instetoo_native
module:
build --all
For details run:
build --help
8build --all
would rebuild changed/missing files.
9The 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).
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). |