Building OpenOffice.org 2.x (680er series) under Windows with MinGW compiler+tcshBeware! The build instructions for OpenOffice.org 1.1.x (and older) are different! Last changes made: $Date: 2006/06/17 17:34:01 $ This document describes the requirements and actions that you need to build OpenOffice.org on Windows using MinGW compiler and Cygwin shell. Commands you have to type on the keyboard follow this syntax throughout this document: config_office> ./configure
In
this example, the script
Table of Contents
OverviewThis section is meant as a reminder or checklist for those who have some experience in building OpenOffice.org. Everybody else should jump to the Build Requirements section. Even experienced builders are well advised to check the release notes at http://development.openoffice.org/releases/2.0.0rc2.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. Overview of Performing a Full BuildTo perform a full build, you need to follow these steps:
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 RequirementsBefore 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: Software Requirements
Perl Module requirementsThis is a list of the perl modules that have to be installed. Important
Note:
No, these modules are not
automatically included in the Cygwin perl installation. Use the
link above to learn how to install them. |
|||||||
Module: |
Used for: |
||||||
Archive::Zip |
packing image lists, evtl. for further zipping needs |
||||||
XML::Parser |
expat based parser for the new XML based build lists |
||||||
Perl - Additional CWS tooling requirementsFor committers who want to use the CWS tooling |
|||||||
Module: |
Used for: |
||||||
Crypt::SSLeay |
for SSL encrypted SOAP connections. Note: It needs the openssl-devel cygwin package to be installed. |
||||||
LWP::UserAgent |
a requirement for SOAP::Lite that is not automatically installed. Install it or the install of SOAP::Lite will fail. |
||||||
SOAP::Lite |
access the SOAP based CWS webservice. |
||||||
Hardware Requirements
External ComponentsThe 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 http://tools.openoffice.org/ext_comp.html.
Get the source codeYou have two options to get the source code:
Generating the Build Environment and Build ToolsThe
This
configuration file is created in the 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 - ExampleEven
though tcsh is the default shell since m83, you should enable the
use of tcsh with To
run the $SRC_ROOT> cd config_office config_office> PATH=/cygdrive/c/mingw/bin:$PATH ./configure --with-mingwin=yes --with-psdk-home="/cygdrive/c/Program Files/Microsoft Platform SDK" --with-nsis-path="/cygdrive/c/Program Files/NSIS" --with-asm-home=/cygdrive/c/WINDDK/3790.1830/bin/x86--with-directx-home="/cygdrive/c/Program Files/Microsoft DirectX SDK (August 2006)" --with-jdk-home="/cygdrive/c/j2sdk1.4.1_03" --with-ant-home="/cygdrive/c/apache-ant-1.6.5" –enable-build-mozilla
There
are a number of options that you can use with the config_office> ./configure --help
After
running $SRC_ROOT> tcsh To create the dmake make utility that is needed for the build of OpenOffice.org type the following command: $SRC_ROOT> ./bootstrap Now source the configuration file which sets all environment variables: $SRC_ROOT> source winmingw.set Don't forget to run $SRC_ROOT> rehash afterwards. If
you experiment with the newest sources from the cvs-tree, mind
that updates to the configure process may not happen via updates
of 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 configure.in config_office> autoreconf
To
update the Build InstructionsBuilding a Full Build of the Office SuiteNow you are ready to build OpenOffice.org. 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 $SRC_ROOT 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 $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 |
Athlon XP1700 |
||||||
Processor speed |
1466 MHz |
||||||
RAM |
512 MB |
||||||
Hard Disk |
160 GB 7200 RPM IDE |
||||||
Time (for SRC680_m86) |
~17 h |
||||||
Building a Project with Debug InformationTo
rebuild a complete project with debug information, remove all
object files by removing the $SRC_ROOT/(module)> rm -rf $SRC_ROOT/(module)> build debug=true
Instructions to Build an Installation SetThe
build process (started with a top-level 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 wntgcci0.pro
The
English installation set will be located at
$SRC_ROOT> cd instsetoo_native/wntgcci0.pro/OpenOffice/install/en-US en-US> setup.exe 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 OpenOffice.org). For
a network installation, use the For information on creating an automated installation script and create a response file.
Building Localized Versions of OpenOffice.orgRunning
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
Example:
The
environment variable
Building Localized Language PacksIf 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 OpenOffice.org 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
|