Building OpenOffice.org under Solaris
This document refers to older versions of OpenOffice.org only. If you intend to build the snapshot No. 638 or later, go here!
This document describes the requirements and actions that you need to build OpenOffice.org on Solaris. Commands you have to type on the keyboard follow this syntax throughout this document:
In this example,
is executed in the directory
$SRC_ROOT will denote the directory in which
the source code of OpenOffice.org is stored.
Table of contens:
- Build Requirements
- Build Instructions
- Building a Full Build
- Building Individual Projects with a Prebuild
- Building a Project with Debug Information
- Instructions to Build an Installation Set
All those who have done a build of OpenOffice.org before may use this section as a reminder. You are well advised to check the release notes at www.openoffice.org/dev_docs/source/download.html and the section Build Requirements in this document to inform yourself about changes since the previous releases.
Detailed step-by-step build descriptions are given from the next section on.
You can perform a full build, or you can build an individual project using a prebuild version.
To perform a full build, you need to follow these steps:
- Get the source code, either from the download webpage at www.openoffice.org/dev_docs/source/get_tarballs.html, or alternatively via a check-out from the cvs tree against a release tag, e.g. OpenOffice614.
configurescript to check all requirements and to create the script
SolarisSparcEnv.Setscript to set all environment variables.
Create the build tools using
bootstrap(unless you want to build the 613 or an earlier version for which the build tools are already provided in the source).
Build using the
You can use a prebuild version to build an individual project. Having a prebuild version is neccessary because the individual project you want to build could depend on other projects. A project builds a particular component of OpenOffice.org. For example, the Word Processing project builds the Word Processing application. To build an individual project, you must follow these steps:
Download the appropriate solver tarballs from the download webpage at
i.e. for 614 the solver tarball
Check out the modules for the project that you want to build from the
OpenOffice.org CVS tree.
If your project uses the resources module,
res, check out this module also. You can, of course, also download the entire source from the download webpage (www.openoffice.org/dev_docs/source/get_tarballs.html). However, it is not possible to download individual modules there.
Check out the module
config_office. This is always necessary to create the build environment.
Also check out the modules
dmake, external, xml2cmp, mkdepend(from 625 on),
sal, vos, tools and rscpp. These are required by
bootstrap(see below). They are not needed for builds 613 or earlier for which the build tools are provided in
- Unpack the solver tarball.
configurescript to check all requirements and to create the script
Run the script
SolarisSparcEnv.Setto set all environment variables.
Create the build tools using
bootstrap(unless you want to build the 613 or an earlier version for which the build tools are provided in the
- Build each module against the prebuild
Before you start building, you must ensure that your system satisfies the recommended software and hardware requirements for the type of system you are working on. For Solaris, these are as follows:
- Solaris 2.8
until 613: Solaris Workshop 5 Compiler and the patch 106327-06
from 614 on: Solaris compiler Forte C++ 6 update 1
- JDK 1.2.2
- Perl 5
from 613 on: STLPort Version 4.0, freely available from
You have to download and install STLPort 4.0. The installation is
described in the files within STLPort 4.0. Put them anywhere you like,
but remember the absolute path to it.
Problems building STLPort? Check issue 693.
from 627 on: The gpc general polygon clipper library release 2.31, located at, for instance,
http://penguinppc.org/files/pub/openoffice/633b/src/ (file gpc231.tar.Z,
the original site - www.cs.man.ac.uk/~amurta/software - is no longer
Download and unpack the tarball. You should have the files
gpc.c and gpc.h in
from 614 to 627: Berkeley DB 3.1.17 from
Download the tarball from their download website
and build the data base following
their instructions given on the documentation website.
Remember that the java API has to be build as well which is not the
default option. This entails the enable java and enable dynamic option
to the configure command. Make also sure that
javacis in your PATH variable. The data base will consist in a directory structure (
db3.1.17) including a subdirectory
java/classes. Go there and create a java archive (
db.jar(db31.jar for older releases) and place this into the
db3.1.17> cd build_unix db3.1.17/build_unix> ../dist/configure --enable-java --enable-dynamic db3.1.17/build_unix> make db3.1.17/build_unix> cd ../java/classes db3.1.17/java/classes> jar cvf db.jar * db3.1.17/java/classes> mv db.jar $SRC_ROOT/external/common/.From 632 on, all necessary components of the Berkeley DB are included in the OpenOffice.org source.
For Solaris/x86: Intel Pentium II PC
For Solaris/Sparc: Sparc Ultra 1
- 128 MB RAM
- 3 GB free disk space
The code contains some further external components which are
already provided. If you are interested in details about these,
look at the External Components webpage at
You have two options to get the source code:
Download the source code tarball from
oo_609_src.tar.gzin case of the 609 release. There is a second source tarball called
solenvcontaining the build tools for some early versions. This tarball has become obsolete with the introduction of the
bootstraputility (explained later) which creates those build tools. However, if you want to build an early version, you have to download this tarball as well.
Unpack the tarballs as follows (for the example 609):
> gunzip oo_609_src.tar.gz > tar -xvf oo_609_src.tar > cd oo_609_srcThis will be $SRC_ROOT from now on.
For releases 613 or earlier you will also need the
$SRC_ROOT> gunzip solenv609_solaris_sparc.tar.gz $SRC_ROOT> tar -xvf solenv609_solaris_sparc.tar
Another possibility is to check out the code from the cvs tree. If you
don't have a username and password, you can still do a checkout as
> runsocks cvs -d:pserver:firstname.lastname@example.org:/cvs login > cd $SRC_ROOT $SRC_ROOT> runsocks cvs / -d:pserver:email@example.com:/cvs / co -r OpenOffice609 openofficeThe non-bold slash means that the command should be in one line. It is possible to update an already existing older copy to a newer release:
$SRC_ROOT> runsocks cvs / -d:pserver:firstname.lastname@example.org:/cvs / update -r OpenOffice609 openoffice
If you're only interested in building individual modules, you won't
need the entire source code. You can check out individual modules from
the cvs tree:
$SRC_ROOT> runsocks cvs / -d:pserver:email@example.com:/cvs / co -r OpenOffice609 (module-name)
You use the
configure script to generate the build environment.
checks that all software, hardware, and system requirements for the build
are satisfied, and it
creates a configuration file called
that you then run the
on to set all necessary build environment variables.
This configuration file will be moved into the
directory. A top-level makefile script
and the script
bootstrap in the
config-office directory will be moved into
as well. This is due to technical reasons: The
in the cvs tree can only hold directories. On the other hand, the
makefile.rc should logically be placed in the
SRC_ROOT. The cvs tree holds these files in
configure copies them up.
In case you adjust the sample file
winenvsample.bat to your
needs rather then running the configure script, you have to copy it by
SRC_ROOT and name it
Copying the file
$SRC_ROOT had to be done by hand as well in this case.
If you experiment with newest sources from the cvs-tree,
mind that updates to the
configure process do not happen via updates of
(the script file) but via the file
configure script itself is created from
autoconf command. In this case, you would
run commands like the following:
$SRC_ROOT> cd config_office config_office> cvs update configure.in config_office> ./autoconfto update the
configurescript. If you only use code from the snapshot releases on the web, you don't need to be concerned about this.
To run the
configure script, type the following commands:
$SRC_ROOT> cd config_office config_office> ./configure --with-stlport4-home=(path)where
pathis the absolute path pointing to your STLPort installation.
configurewill probably also ask you for the location of the Java Development Kit 1.2.2.
There are a number of further options that you can use with the
script. To display these options, type the following command:
config_office> ./configure --help
--with-stlport4-home is a requirement.
For more information on the options that you can use with the
configure script, see the Build Environment document at
configure, you have to source the configuration
file with sets all environment variables:
$SRC_ROOT> tcsh $SRC_ROOT> source SolarisSparcEnv.Set
To create the build tools, type the following command:
bootstrap utility creates the tools required for building.
This involves already building some modules and will take a few minutes.
$SRC_ROOT> dmakeIf you are interested in the order in which the individual modules are build, type
$SRC_ROOT> dmake -n
The following table shows the time required to build on a system with a particular specification. You can use these details to estimate the time required to build on your system.
|Hard disk size||4 GB IDE|
OpenOffice.org is organised in several projects. For example, the Word Processing Project. These in turn consist of several modules, organised in separate directories. The source contains approximately 90 modules.
You can build any project or module individually. Building modules
individually should not be misunderstood as reducing OpenOffice.org to a
special application, say, for instance, the spreadsheet application. The
program will always consist in the entire office suite: text processor,
spreadsheet, drawing application etc.. Building individual
modules comes in handy if you want to develop on a certain module.
Most modules will
depend on other modules to be already built. In other words, all modules
must build in a particular order.
To avoid building all modules which are prerequisites of the
module of your interest,
you can make use of a pre-build
against which you can build any module.
For more information on modules and on the sequence that they build in, and on the dependencies, see tools.openoffice.org/modules.html.
You have to download the
solver tree as a tarball
from the Download page at
and unpack it in the
$SRC_ROOT> gunzip solver609_solaris_sparc.tar.gz $SRC_ROOT> tar -xvf solver609_solaris_sparc.tarIn order to create the build environment and build tools (bootstrap), you also have to check out the modules
config_office, dmake, external, xml2cmp, mkdepend(from 625 on),
sal, vos, tools and rscpp. Except for
config_office, they are not needed for builds 613 or earlier for which the build tools are provided in
To build a project, you build each of its modules individually
in their directory with the
$SRC_ROOT/(module-name)> dmakeFiles called
makefile.rcin each directory with further subdirectories iterate through all directories of the module and exectues
dmakein each of them (just like the top-level
makefile.rcdoes when building the entire office suite). The last or second to last directory is usually module-name
/utilwhich is responsible for linking one or more shared libraries.
To rebuild a complete project with debug information, remove all object
files by removing the
directory. Then run
dmake with the debug option set to true:
$SRC_ROOT/(module)> rm -rf unxsols3.pro $SRC_ROOT/(module)> dmake debug=true
When you have completed the build, you need to do the following to install and set up the office suite:
From the top-level directory, run the
dmake installcommand, or run
dmakein the directory
$SRC_ROOT> dmake installor
$SRC_ROOT> cd instsetoo instsetoo> dmakeLanguages other than english (provided the language option was set in configuring) can be build with the option
LANGEXT. For instance for french:
$SRC_ROOT/instsetoo> dmake LANGEXT=33The parameter 33 stems from the international phone code for France.
Change directory to
$SRC_ROOT/instsetoo/unxsols3.pro/normaland execute the
$SRC_ROOT> cd instsetoo/unxsols3.pro/normal normal> ./setup