The Free and Open Productivity Suite
Apache OpenOffice 4.1.7 released

Building 1.1.x under Windows with tcsh

Beware! The build instructions for 2.x are different!

The Cygwin tcsh environment is new (from December 2003), and can be used starting with cws_srx644_ooo20030412.

This document describes the requirements and actions that you need to build on Windows using Cygwin shell.

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.

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

Basically, there is the choice to build from two different branches: a stable branch, which results in the release version, or a less stable developer branch (latest release see here). Links to the different sources are given in the document.

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.

You can perform a full build, or you can build an individual project using a prebuilt version.

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_1_1_4.
  2. Run the configure script to check all requirements and to create the script winenv.set.
  3. Run the winenv.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. Build typing dmake in $SRC_ROOT, or build --all in the instsetoo 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.

Overview of Building an Individual Project

You can use a prebuilt version to build an individual project. Having a prebuilt version is necessary because the individual project you want to build could depend on other projects. A project builds a particular component of For example, the Word Processing project builds the Word Processing application. To build an individual project, you must follow these steps:

  1. Download the appropriate solver tarballs from the download webpage ( e.g., for 643B the solver tarball solver643B_win32intel.tar.gz.

    643 is a very old release. Please use the latest version.

  2. Check out the modules for the project that you want to build from the 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 ( However, it is not possible to download individual modules there.
  3. Check out the module config_office. This is always necessary to create the build environment.
  4. Also check out the modules dmake, external, sal, solenv, soltools, vos, tools, rsc and xml2cmp. These are required by bootstrap (see below).
  5. Unpack the solver tarball in the $SRC_ROOT directory.
  6. Run the configure script to check all requirements and to create the settings file winenv.set.
  7. Run in tcsh source winenv.set and rehash afterwards or in bash source to set all environment variables and build dmake.exe.
  8. Create the build tools using ./bootstrap.
  9. Build each module against the prebuilt solver using the build tool, followed by deliver.
For detailed build instructions, see Building Individual Projects with a Prebuilt.

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 Windows, these are as follows:

Build Requirements

Perl - Optional requirements

For committers who want to use the CWS tooling. Install them like this.

Module: Used for:
Crypt::SSLeay for SSL encrypted SOAP connections
SOAP::Lite access the SOAP based CWS webservice

Hardware Requirements

External Components

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

Get the source code

You have two options to get the source code:

Generating the Build Environment and Build Tools

You use the configure script to generate the build environment. The configure script checks that all software, hardware, and system requirements for the build are satisfied, and it creates a configuration file called winenv.set that you then run the source command on to set all necessary build environment variables. Don't forget to run rehash afterwards.

This configuration file will be moved into the SRC_ROOT directory. A top-level makefile script and the script bootstrap in the config-office directory will be 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.

Before running configure, make sure that all needed Programs are in the system path or start configure with the appropriate command line switches.

The following should demonstrate in detail what steps have to be done to set up the environment. For this examples we assume that

tcsh - Example

You have to enable the use of tcsh with --with-use-shell=tcsh.

To run the configure script, type the following command:

$SRC_ROOT> cd config_office
config_office> ./configure --with-cl-home="/cygdrive/c/Programme/Microsoft Visual Studio .NET 2003/Vc7"
--with-asm-home=/cygdrive/c/ml --with-jdk-home=/cygdrive/c/j2sdk1.4.1_02

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 source the configuration file which sets all environment variables:

$SRC_ROOT> tcsh

$SRC_ROOT> source winenv.set

Don't forget to run

$SRC_ROOT> rehash

afterwards. See the last screen from configure for exact details for your platform.

If you experiment with 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.

To create the build tools, type the following command:

$SRC_ROOT> ./bootstrap

The bootstrap utility creates the tools required for building. This involves already building some modules and will take a few minutes.

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 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 Intel
Processor Pentium III
Processor speed 600 MHz
RAM 256 MB
Hard Disk 6 GB SCSI
Time ~10 h

Building Individual Projects with a Prebuilt 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 to a special application, say, for instance, the spreadsheet application. The program will always consist of 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 prebuilt solver tree 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

You have to download the solver tree as a tarball. For example solver643B_win32int.tar.gz from the Download page at, use a current release 643 is very old and only used as an example, and unpack it in the $SRC_ROOT directory, e.g.:

$SRC_ROOT> tar -xvzf solver643B_win32int.tar.gz

In order to create the build environment and build tools (bootstrap), you also have to check out the modules config_office, dmake, external, xml2cmp, mkdepend, sal, solenv, vos, tools and rscpp.

To build a project, you build each of its modules individually in their directory with the build tool, followed by deliver to copy the created libraries, binaries etc. into the solver tree:

$SRC_ROOT/(module-name)> build
$SRC_ROOT/(module-name)> deliver
Files called build.lst in the directories (module-name)/prj contain all information about the subdirectories to be build (each of them containing makefiles, about internal dependencies, and also about modules the current module depends on. The files (module-name)/prj/d.lst control the actions done by deliver. The last or second to last directory to be build is usually module-name/util which is responsible for linking one or more shared libraries.

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) will create installation sets in English and German. A simple build in $SRC_ROOT/instsetoo 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> rm -rf

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

$SRC_ROOT> cd instsetoo/
normal> setup.exe
The 01 in the path names indicates that the localisation is American English. This number corresponds to the international phone code for the USA. The German installation set will be located in a subdirectory 49. This scheme holds true for all localisations you may have chosen explicitly (see next section Building Localised 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 Localised Versions of

Running the configure script with the --with-lang option will introduce the build of additional language resources. This option will introduce a command in the environment settings file which in turn after execution sets a variable like, for instance, RES_FREN to TRUE in the case of french (You can also set this variable by hand in order to introduce another language). It is also possible to build more than one language at once. One language resource, however, will not be introduced that way: the help content! Clicking on 'help' would still open English help documents.

There is no automatic procedure yet to implement non-English help, but the additional manual effort is rather minimal: After building the source as described above, but before building the installation set, a zip-file with all help-content for the language of choice has to be unzipped into the directory


The filenames of these files contain a number code for the language, corresponding to the international phone code of a country in which that language is mainly spoken. For instance, the file contains all help content for the Spanish localisation. The zipfiles themselves are available at

Having unzipped the helpcontent files in there, building of installation sets can be resumed or repeated (in case you already have build some), as described in the previous chapter. English installation sets will be located in

where 01 corresponds to the international phone code of the USA. If you have chosen, for instance, French (by configuring with the --with-lang=FREN option) you will find an additional directory called 33:

Similarly, you will find 49 for German, 34 for Spanish, etc.

Localised help content is not yet available for all languages. In such cases, the English helpcontent will appear in the installations. For instance, when Danish is set with configure, you will find installation sets under the directory 45, but the help files will appear in English.

Apache Events

Apache Software Foundation

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

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