The Free and Open Productivity Suite
Released: Apache OpenOffice 4.1.15


Much of the information here is outdated and refers to obsolete OOo versions.

For current information on how to build OOo, see the OOo Wiki: Building Guide

Building 2.x (680er/300er series) under Solaris

Beware! The build instructions for 1.1.x (and older) are different!

Last changes made: $Date: 2010/06/08 16:09:13 $

This document describes the requirements and actions that you need to build on Solaris.

Commands you have to type on the keyboard follow this syntax throughout this document:

config_office> ./configure

In this example, the script configure is executed in the directory config_office.

Since 2.1.x (SRC680_m175) it is possible to use bash instead of tcsh. This has to be enabled with the --with-use-shell configure switch. The following instructions are for the tcsh case but the savy *NIX user should be able to guess the needed changes. The environment file for bash adds an additional .sh suffix to the tcsh environment filename.

$SRC_ROOT will denote the directory in which the source code of is stored.

Table of Contents


This section is meant as a reminder or checklist for those who have some experience in building Everybody else should jump to the Build Requirements section.

Even experienced builders are well advised to check the release notes at 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.

Overview of Performing a Full Build

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

  1. Get the source code, either from the download webpage ( or alternatively via a check-out from the cvs tree against a release tag, e.g. OpenOffice_3_1_0.
  2. Run the configure script to check all requirements and to create the script SolarisSparcEnv.Set.
  3. Source the SolarisSparcEnv.Set script to set all environment variables.

    Please see the last screen from the configure script for more specific information on setting up for your platform.

  4. Create the build tools using bootstrap.
  5. Recompute tcsh's directory hash using rehash.
  6. Build typing dmake in $SRC_ROOT, or build --all in the instetoo_native module, or build followed by deliver in the individual modules.
For detailed build instructions, see the section Building a Full Build of the Office Suite in this document. The installation procedure is described at the end of this document.

Build Requirements

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:

see Solaris Build Requirements

Get the source code

You have two options to get the source code:

Generating the Build Environment and Build Tools

The configure script to check/prepare the build environment. It checks that all software, hardware, and system requirements for the build are satisfied, and creates a configuration file called SolarisSparcEnv.Set that is used to set all necessary build environment variables. See the example below.

This configuration file is created in the SRC_ROOT directory. A top-level makefile script and the script bootstrap from the config-office directory are moved into SRC_ROOT as well. This is due to technical reasons: The SRC_ROOT directory in the cvs tree can only hold directories. On the other hand, the top-level should logically be placed in the top-level directory SRC_ROOT. The cvs tree holds these files in config_office and configure copies them up.

If you are running a compiler with a non-standard name or location make sure that the environment variables CC and CXX point to your c and c++ compiler. (This can also be used to to use ccache to reduce your compile time.)

export CC=/your/path/to/cc
export CXX=/your/path/to/CC

To run the configure script, type the following command:

$SRC_ROOT> cd config_office
config_office> ./configure

There are a number of options that you can use with the configure script. To display these options, type the following command:

config_office> ./configure --help

After running configure, you have to continue in a tcsh shell:

$SRC_ROOT> tcsh

To create the dmake make utility that is needed for the build of type the following command:

$SRC_ROOT> ./bootstrap

Now source the configuration file which sets all environment variables:

$SRC_ROOT> source SolarisSparcEnv.Set

Don't forget to run

$SRC_ROOT> rehash


If you experiment with the newest sources from the cvs-tree, mind that updates to the configure process may not happen via updates of configure (the script file) but via the files and The configure script itself is created from using the autoreconf command. The perl script set_soenv is created when you run configure from

If you need to modify or create a correct configure you would run commands like the following:

$SRC_ROOT> cd config_office
config_office> cvs update
config_office> autoreconf
To update the configure script. If you only use code from the snapshot releases on the web, you don't need to be concerned about this.

Build Instructions

Building a Full Build of the Office Suite

Now you are ready to build To build the entire suite, all you have to do (after having created the environment as described above) is to run dmake from the top-level directory. This may take several hours.
$SRC_ROOT> dmake

If you wish to control the build more you can perform a build with local install sets or tarballs.

	cd instetoo_native
	build --all

If you decide to rebuild a module or build each module individually (mind dependencies!), you will have to use the build tool. A subsequent deliver will copy all created binaries, libraries etc. into the solver tree:

$SRC_ROOT/(module)> build
$SRC_ROOT/(module)> deliver

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.

Architecture SPARC
Model Ultra 30
Processor speed 300 MHz
RAM 512 MB
Hard disk 10000 RPM model
Time (for SRC680_m74) ~39 h

Building a Project with Debug Information

To rebuild a complete project with debug information, remove all object files by removing the directory. Then run build with the debug option set to true:

$SRC_ROOT/(module)> rm -rf
$SRC_ROOT/(module)> build debug=true

Instructions to Build an Installation Set

The build process (started with a top-level dmake or build --all in $SRC_ROOT/instsetoo_native) will create an installation sets in English. A simple build in $SRC_ROOT/instsetoo_native will also create the installation sets, provided all other modules are already built.

If you have built an installation set earlier and want to re-build it, please delete the local outpath first:

$SRC_ROOT/instsetoo_native> rm -rf

The English installation set will be located at $SRC_ROOT/instsetoo_native/ Execute the setup binary to install:

$SRC_ROOT> cd instsetoo_native/
en-US> ./setup
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 next section Building Localized Versions of

For a network installation, use the -net option to setup. Details on the network installation process can be found at in the installation project webpage.

For information on creating an automated installation script and create a response file.

Building Localized Versions of

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, unfortunately not all languages are supported. Check the value of the completelangiso macro in $SRC_ROOT/solenv/inc/ for all the currently supported language tags.

Example: --with-lang="de fr" enables the build of the localized german and french version.

The environment variable WITH_LANG will then contain the language tags of the additional (en-US will always be build) languages.

Building Localized Language Packs

If you build additional localized languages it is possible to generate Language Packs that contain only the changes needed to add the additional language to an of a different language.

The following commands will generate language packs languages that were specified with the --with-lang switch during the configure phase. Note that you can only build the language packs after you have build the complete office with all selected languages.

$SRC_ROOT> cd instsetoo_native/util; dmake ooolanguagepack

Apache Software Foundation

Copyright & License | Privacy | Contact Us | Donate | Thanks

Apache, OpenOffice, and the seagull logo are registered trademarks of The Apache Software Foundation. The Apache feather logo is a trademark of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.