Apache OpenOffice Wiki - User contributions [en]

Documentation/Building Guide/Building on Windows with MinGW

2011-02-10T11:35:37Z

Tono:

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}

{{DISPLAYTITLE:Building on Windows with MinGW}}
[[Category:Windows]]
{{Documentation/DraftPage}}

__TOC__

= Overview =

{{Template:Documentation/Windows| This document explains how to build the OpenOffice.org source code on Windows systems with MinGW compiler and linker.}}

== what is MinGW? ==
MinGW stands for Minimalist’s GNU for Windows. It is a set of firee, open source software including compiler, linker,shell environment and other useful tools for developing software. MinGW is intended to support developing software to work on Microsoft 32-bit Windows with minimal support of external libraries. The MinGW community is distributing the g++ compiler from gcc (GNU compiler collection) and GNU ld linker for Windows 32-bit executables in GNU binutils, which is a set of tools to manipulate binary object and executable files.

== the reason why MinGW build is being maintained ==
Please note the official releases of OpenOffice.org for Windows are built using tools from Microsoft. The build with MinGW compiler and linker is being maintained for checking the code portability and keeping the alternative to Microsoft tools. Microsoft compiler does not complain at some codes violating C++ standard and although Microsoft is supplying Visual Studio Express edition free of charge for the time being, they may stop to do so in the future. And it may make sense to keep OOo to be buildable with open source tools.

== Cygwin ==
For building OpenOffice.org Cygwin is needed, a Windows program that emulates a complete Unix command line environment. To use this document you need to be familiar with a command line, but you need not to be a UNIX shell wizard.

{{Template:Documentation/Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}

{{Template:Documentation/Note|<tt>$SRC_ROOT</tt> will denote the directory in which the source code of OpenOffice.org is stored.}}
{{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.}}

== Cygwin compiler v. s. MinGW compiler ==
Cygwin also includes C++ compiler and linker in its distribution as well as headers and libraries of MinGW. Specifying -mno-cygwin command line switch, the tools can generate the same object code to MinGW compiler. However, as the tools use Cygwin system call to invoke sub programs, the process to build OpenOffice.org with Cygwin’s compiler and linker is a bit slower and more unstable than that with “pure” MinGW tools on Cygwin shell.
== versions and problems in compiler and linker ==
The version of the official release of gcc from MinGW is gcc-3.4.5 for version 3 series and gcc-4.4.0 for version 4 series. 4.4.0 is the first official release of version 4 series and older versions in version 4 series were all experimental. Cygwin includes gcc-3.4.4 and experimental 4.3.2.
Compilers of version 3 series have several problems to build OOo and needs patches. You can get the patched binaries of core C compiler and C++ compiler at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Available version is only 3.4.4. The source patch is also available there. You can get the patched compilers equivalent to them in Cygwin distribution. You have to get core C compiler, C++ compiler and the MinGW libraries for both C and C++ at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Please note that you have to run the postinstall command in /etc/postinstall directory after extracting the distribution of both of the MinGW libraries for C on Cygwin and that for C++ under root directory in Cygwin command prompt.
Compilers of version 4 series have no serious problem to build OOo but the standard C++ library distribution included in the official release of gcc-4.4.0 is only partial and needs to be rebuilt using a Cygwin shell script.
Gcc version 4 emits better code and useful warning messages. However, you should concern licence agreements of dlls. MinGW gcc compiler has restriction to use dynamic linking of the two library libgcc and libstdc++ for proper exception handling and the dlls will be included in the installation set you will build. In the meantime the licence agreements of these dlls have a rather strict term to follow if you redistribute them.
The version of the official release of binutils from both MinGW and Cygwin is 2.19.18 and ld linker has problems to build OOo. The patched binaries and sources are available at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net].
== w32api and MinGW runtime library ==
The set of libraries and headers to let code to use Windows API is distributed as w32api. The version 3.13 is required for building OOo. Some new APIs and constant definitions that are not officially published from Microsoft are not included and you have to use files in Microsoft SDK with smalll patches. MinGW runtime library of version 3.16 is required as well to enable multithreading and fix some C functions. MinGW tools are intended to use Microsoft C runtime library that is always installed in Windows system but some bugs are fixed in MinGW runtime library.
= Requirements =
== hardware requirements ==

* 1 or more reasonable fast CPUs (x-way CPU recommended)
* 1 GB RAM (2 GB recommended)
* 10 GB free disk space (20 GB when debugging)

== software requirements ==
* Windows XP/Vista

The following table is placed here, so you can come back to it easily, when you want to use a link. The items are explained below. Here's the list of files to download (with links) and the locations in the source tree where you must put them:

{| class="prettytable" border="1" width="100%"
|-
! Where to get
! Place in
|-
| Cygwin: [http://www.cygwin.com Cygwin Toolkit with (dll version 1.5.10) or later]
| (default)
|-
| Either of
“pure” gcc 3 series tools including patched “pure” MingW gcc 3 compiler and patched binutils: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools gcc-core-3.4.4-20050522-1-ooopatched.tar.gz gcc-g++-3.4.4-20050522-1-ooopatched.tar.gz binutils-2.20.1-ooopatched.tar.gz] and w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

“pure” gcc 4 series tools including patched binutils and the library rebuilding script: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools binutils-2.20.1-ooopatched.tar.gz gcc-core-g++-4.4.0-install.sh] and MingW gcc 4 compiler, w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ gcc-core-4.4.0-mingw32-bin.tar.gz gcc-core-4.4.0-mingw32-dll.tar.gz gcc-c++-4.4.0-mingw32-bin.tar.gz gcc-c++-4.4.0-mingw32-dll.tar.gz gmp-4.2.4-mingw32-dll.tar.gz mpfr-2.4.1-mingw32-dll.tar.gz pthreads-w32-2.8.0-mingw32-dll.tar.gz w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

Cygwin tools including patched Cygwin gcc 3 compiler and patched binutils (w32api and MinGW runtime for Cygwin compiler/linker are included in Cygwin distribution): [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools/cygwin gcc-core-3.4.4-3ooopatched.tar.bz2 gcc-g++-3.4.4-3ooopatched.tar.bz2 gcc-mingw-core-20050522-ooopatched-1.tar.bz2 gcc-mingw-g++-20050522-ooopatched-1.tar.bz2 binutils-2.20.51-2-ooopatched.tar.bz2]
| (default)
|-
| Java: [http://java.sun.com/javase/6/ JDK 1.6] for DEV300 milestones >= m37 and all OOo310 versions (older milestones will fail in the hsqldb module)
| (default)
|-
| [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008].<ref name="Foot1">{{Template:Documentation/Note|This also supported on Vista. This is either a DVD image or a net installer. You can either mount the DVD with a suitable tool, burn it do a DVD or use tools like winrar that can extract files from ISO files directly. You don't need to install samples or documentation (saves a lot of disk space). It will also install the .NET Framework 3.5 SDK.
It might be best to install the Windows SDK into the default directory, and if not that into one without capital letters in the path. I used D:\Dev\Win_SDK\ and received some linking errors in the Python module (see {{Bug|88568}}).}}</ref>
|
|-
| [http://www.microsoft.com/downloads/details.aspx?familyid=6A63AB9C-DF12-4D41-933C-BE590FEAA05A&displaylang=en GDI+ Redistributable] (Genuine Windows Validation required)
| external/gdiplus
|-
| Only for OOo2.x but due to {{Bug|88652}} in configure still needed for 3.x: [http://download.microsoft.com/download/b/7/5/b75eace3-00e2-4aa0-9a6f-0b6882c71642/unicows.exe unicows.dll from (Microsoft Layer for Unicode)]<ref name="Foot2">{{Template:Documentation/Note|unicows.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/unicows. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
| external/unicows
|-
| [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CD1FC4B2-0885-47F4-AF45-7FD5E14DB6C0 dbghelp.dll]<ref name="Foot3">{{Template:Documentation/Note|dbghelp.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/dbghelp. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>

| external/dbghelp
|-
| [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/NT45/EN-US/InstMsiW.exe instmsiw.exe] and [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/W9XMe/EN-US/InstMsiA.exe instmsia.exe]
| external/msi
|-
| [http://archive.apache.org/dist/ant/binaries Apache Ant (version 1.6.5 or later)]
| (default)
|-
| either of [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_moz Mozilla binary distribution] for milestone <= DEV300_m52 or [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_seamonkey Seamonkey] for milestone >= DEV300_m53

| moz/zipped
|-
| optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)]<ref name="Foot5">{{Template:Documentation/Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}

{{Template:Documentation/Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}</ref>
|
|-
| optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK]<ref name="Foot6">{{Template:Documentation/Note|If you don't want to download it you can disable DirectX support in the configuration step (<tt>--disable-directx</tt>).}}

{{Template:Documentation/Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}

{{Template:Documentation/Caution|Do not use a DirectX10 SDK!}}</ref>
|
|-
| optional: [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild]
|
|}
=== adding required files to the build tree ===

{{Template:Documentation/Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}

{{Template:Documentation/Note|OOo uses some Mozilla libraries. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}

= Installation and Preparation of Build Tools =
== setting up cygwin ==

Go to http://www.cygwin.com/ and download and install the current version.
{{Template:Documentation/Caution|Make sure that you keep the filetype set to “Unix/binary”.}}

=== required additional packages ===
Cygwin consists of some basic and a lot of optional packages. As building OOo needs some of these optional packages you have to select them in the installer.
Here's a complete list of the needed packages:
* Category Archive:
** cabextract
** unzip
** zip
* Category Devel :
** autoconf
** bison
** flex
** gcc-g++
** gperf
** make
** openssl-devel (only needed for perl modules for CWS tooling, see below)
** pkgconfig
** cvs (for 2.x code line and 3.0 code line)
** subversion (for 3.x code line, minimum version 1.5.5)
* Category Libs
** openssl
* Category Net
** openssh
** ncftp
** rsync
* Category Perl
** perl
* Category Shells
** rxvt
* Category Utils
** file
** patch
** gnupg
* Category Web
** lynx
** wget
{{Template:Documentation/Caution|You have to exclude the package rebase in Category Base if you use Cygwin compiler for OOo build.}}
{{Template:Documentation/Note|Unfortunately the list of packages mentioned at http://website.openoffice.org/support/en/howtos/1.html#1 is incomplete, some more are listed at http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#BuildRequirements .}}

{{Template:Documentation/Note|The installer will automatically check and download some more packages needed by thosed listed here. The whole process takes roughly 20 minutes.}}

=== breaking links to executables ===
Within the Cygwin Toolkit, some executables might be symlinks: awk.exe and gunzip.exe, tar.exe (in older releases only). This can lead to a break of the build later, and the symlinks should be replaced by copies of the command they link to.

To check this, execute:

ls -l /bin/awk.exe

whether e.g. awk.exe is a symlink. In version 1.5.24-2 awk.exe is a link to gawk.exe. The shell will show this by putting out “awk.exe -> gawk.exe”. In this case gawk.exe must be copied to awk.exe by executing:

cd /bin
rm awk.exe
cp gawk.exe awk.exe

In case you overlook something here or you have a newer Cygwin version with additional symlinks not mentioned here it's not a problem. You will get a helpful error message about an existing link in the configuration step (configure) later. The message will tell you which link you have to remove and you can do it following the advice given above for the awk.exe/gawk.exe pair.

=== installing additional perl modules in cygwin ===
As explained some perl modules must be installed with CPAN. The necessary command in the cygwin shell is

perl -MCPAN -e shell

If this command is executed the first time CPAN will ask for configuration. Choose autoconfiguration.

{{Template:Documentation/Caution|Please note that CPAN is not able to deal with usernames containing spaces. To work around this fact, when CPAN asks you to specify the ''CPAN build and cache directory'', change the default suggestion to <tt>/cpan</tt>.}}

At the end the CPAN shell appeared and is ready to accept commands for installations. Each module is installed by typing <tt>install $MODULENAME</tt>. The modules that must be installed are:

* Archive::Zip
* XML::Parser (though it seems that this is already installed; doesn't hurt to do it)
* URI
* LWP::UserAgent
* Crypt::SSLeay
* SOAP::Lite

CPAN will detect if a selected module depends on other modules and it will offer to download them also. As explained please just confirm this.

{{Template:Documentation/Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}

{{Template:Documentation/Caution|I got an error message from CPAN somewhat like the following:
<pre>C:\cygwin\bin\perl.exe: *** unable to remap C:\cygwin\bin\cygiconv-2.dll to same
address as parent(0x7C0000) != 0x7D0000</pre>
To fix this, I had to exit the Cygwin shell, run cmd.exe, then type "c:\cygwin\bin\ash.exe" to start the minimal shell, then type <tt>/bin/rebaseall</tt>. Then CPAN worked when I ran it again.}}

{{Template:Documentation/Caution| I got another error when cygwin was performing <tt>make install</tt>:
<pre>ERROR: Can't create '/usr/bin'; Do not have write permissions on '/usr/bin'</pre>
I can actually write to /usr/bin; however when I do <tt>ls -ld /usr/bin</tt>, cygwin reports no write permission; and <tt>chmod u+w /usr/bin</tt> gives <tt>Permission denied</tt>. This causes the install process to fail when it checks permissions. As a kludge, I installed vim, and edited line 368 of /usr/lib/perl5/5.10/ExtUtils/Install.pm, replacing this:
<pre>return -w $dir;</pre>
with this:
<pre>return 1;</pre>
which allowed installation to proceed.}}

== installing compiler and binutils ==
=== installing “pure” MinGW gcc version 3 series compiler and binutils ===
To install “pure” MinGW gcc version 3 series compiler and binutils, you have to create a unique directory first, say <tt>c:/mingw</tt>. All you have to do is to extract all tarballs here.

tar -C c:/mingw -xvzpf xxx.tar.gz

=== installing “pure” MinGW gcc version 4 series compiler and binutils ===
To install “pure” MinGW gcc version 4 series compiler and binutils, you have to choose a unique directory name, say <tt>c:/mingw</tt>, put everything you downloaded in one working directory and invoke the following command in the directory.

./gcc-core-g++-4.4.0-install.sh c:/mingw

Extend the path to get the right compiler:

export PATH=/cygdrive/c/mingw/bin:$PATH

=== installing Cygwin gcc version 3 series compiler and binutils ===
You have to extract all tarballs in root directory.

tar -C / -xvjpf xxx.tar.gz

The tarballs for gcc-mingw-gcc and gcc-mingw-g++ include postinstall scripts. You have to run them to complete installation.

/etc/postinstall/gcc-mingw-core.sh
/etc/postinstall/gcc-mingw-g++.sh

= Full Builds =
== configure ==
Finally the <tt>configure</tt> tool is used to create the environment. It checks that all software, hardware, and system requirements for the build are satisfied, and creates configuration files called winmingw.set (for tcsh) and winmingw.set.sh (for bash) that are used to set all necessary build environment variables. Before running configure, make sure that all needed programs are in the system path or start configure with the appropriate command line switches. If configure detects a problem it will stop and give you a useful hint how to fix it.

You will find the <tt>configure</tt> script in <tt>$SRC_ROOT</tt>. The resulting configuration files are created there too.

==== sample configure calls ====

./configure \
--with-mingwin=yes \
--disable-directx \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS

./configure \
--with-mingwin=yes \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS \
--enable-crashdump \
--enable-symbols=SMALL \
--enable-vba \
--enable-minimizer \
--enable-presenter-console \
--enable-pdfimport \
--enable-wiki-publisher \
--enable-report-builder \
--enable-cairo

==== configure settings tips ====
{{Template:Documentation/Caution|Make sure that the <tt>PATH</tt> variable in your cygwin shell does not contain any blanks and quotes.}}
{{Template:Documentation/Caution|Paths might have problems with spaces. Install requirements into paths without them. Alternatively, feel free to install the various packages using the default path containing spaces and then use the mixed short path for the configure stage. The mixed short path can be obtained using Cygwin's cygpath tool, eg:
<pre>$ cygpath -m -s "c:\Program Files\Microsoft SDKs"
c:/PROGRA~1/MI2578~1</pre>
The <tt>with-psdk-home</tt> setting needs a case-sensitive path name. I recommend to use case-sensitive usage in all cases - it's good to get used to case sensitivity if you are going to work with Cygwin.}}
{{Template:Documentation/Caution|Beware of using <tt>/c/</tt> instead of <tt>/cygdrive/c/</tt>.}}
{{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <tt>--with-psdk-home</tt>.}}
{{Template:Documentation/Note|Paths to dependencies might be different for your installation. The paths containing "msvc" and "msdk" should be self-explanatory.}}
{{Template:Documentation/Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
<pre>./configure --help</pre>}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <tt>WINDOWS_VISTA_PSDK</tt> to be set <tt>TRUE</tt>. This is important if <tt>configure</tt> fails to detect the Windows platform SDK version correctly. The detection failure results from the way that <tt>configure</tt> searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <tt>DISABLE_ATL</tt>, <tt>DISABLE_ACTIVEX</tt>: all have to be set <tt>TRUE</tt>. If you want to build the OOo ActiveX control, OLE automation and native Windows OLE support, you have to copy atl headers from old release of Microsoft Platform SDK.}}
{{Template:Documentation/Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <tt>--disable-directx</tt> as shown above. Otherwise you have to provide the path to the SDK in <tt>--with-directx-home</tt>.}}
{{Template:Documentation/Tip|OOo uses some Mozilla components. Disabling the Mozilla components completely with <tt>--disable-mozilla</tt> currently might not work due to a bug in the module dependencies.}}
{{Template:Documentation/Tip|If you experiment with the newest sources, mind that it can happen sometimes that <tt>configure.in</tt> was updated, but it was forgotten to update configure too. The configure script itself is created from <tt>configure.in</tt> using the <tt>autoreconf</tt> command. The perl script <tt>set_soenv</tt> is created when you run configure from <tt>set_soenv.in</tt>.}}
{{Template:Documentation/Tip|csc.exe comes from the <tt>c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</tt> directory, you might need <tt>--with-csc-path</tt>.}}
{{Template:Documentation/Tip|If you fail to getting together a working installation of Cygwin, one possibility is to use a known-to-work combination of Cygwin packages, i.e. a direct copy of some other user's Cygwin tree. [[User:TorLillqvist]] has such a tree (from late 2006) zipped up at http://download.go-oo.org/tstnvl/tml/tml-cygwin.zip . Don't hesitate to ask for advice if necessary.}}

== bootstrap ==
After running configure you must create the dmake make utility that is needed for the build of OpenOffice.org. This done from the SRC_ROOT directory by calling

./bootstrap

== setting the environment ==

When the configure script has been run successfully a file <tt>winmingw.Set.sh</tt> was created<ref name="Foot7">{{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <tt>winmingw.Set</tt> instead:
<pre> source winmingw.Set
rehash</pre>
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.}}</ref>. Do this:

source winmingw.Set.sh

to set up the environment for the build.

== starting the build ==
Build the software by typing the following in <tt>$SRC_ROOT</tt> <ref name="Foot8">{{Template:Documentation/Note|You can also run:
<pre>make</pre>
but GNU/make will just start dmake. You can also run the following in the <tt>instetoo_native</tt> module:
<pre>build --all</pre>
For details run:
<pre>build --help</pre>}}</ref>:
dmake

The building procedure will take at least an hour (on a 3 GHz Quad-Core with 8GB RAM).

There are some special things in the way how OOo builds its modules. Every module has an “output” folder (with some subfolders for the different kinds of generated output) that is created the first time a build is done in the module. The name of this folder is “wntgcci.pro” (for the meaning of the "pro" extension see below). After a successful build of a module some of the generated files are copied to the output folder of the “solver” module by executing a tool called “deliver” (this is automatically called by build --all for each of the modules). Other modules will take these “delivered” files (header files, libraries etc.) to resolve their dependencies. The content of the solver module will also be used to pack the installation sets in the final step.

{{Template:Documentation/Tip|Using some not quite latest cygwin releases (1.5.18/1.5.19) can lead to tcsh freezing in places - the build will appear to hang. You can fix this by running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
<pre>ls /proc/*/fd</pre>
to "unhang" the process. See {{Bug|51560}} for more info...}}

= Partial Builds =
There are two ways to do partial builds:
* compatible
* incompatible
Only do compatible partial builds if you know exactly what you are doing.
{{Documentation/Note|For more information, see [[Compatible Builds]].}}
== rebuilding from a module (incompatible build) ==

If you decide to change 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

== rebuilding a module (compatible build) ==

To rebuild a module you can delete all output directories with, rebuild and redeliver into the solver with:

cd $MODULE
build --from $MODULE --prepare
build && deliver

A simple <tt>build</tt> in <tt>$SRC_ROOT/instsetoo_native</tt> will recreate the installation sets, provided all other modules have already been build. <ref name="Foot9">{{Documentation/Caution|<tt>build --all</tt> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <tt>build --from --prepare</tt>.}}</ref>

= 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 debug=true --from $MODULE

Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.

{{Template:Documentation/Tip|For details, see [[Windows Debugging]].}}
= Finding the Installation Sets =
After a successful build you will find the OOo installation set in

instsetoo_native/wntmscixx.pro/OpenOffice/msi/Install/en-US

“instsetoo_native” is the module that packs the installation set.

{{Documentation/Tip|If you already have a version of OOo installed you can install your freshly built version in parallel by installing it with setup /a that just unpacks all files without any system registration.}}

= Tips And Tricks =
== ccache ==
For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers
== dependencies ==

'''nodep'''

If you set the environment variable <tt>nodep</tt> to <tt>TRUE</tt>, then dependendy information files are not created - the build finishes faster.

{{Template:Documentation/Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}

'''NO_HIDS'''

Similar to the <tt>nodep</tt> variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile (directory) level, the other one on the global level. The two levels of parallelism result from the two-step build procedure in the OOo build environment. The build script runs through all the directories it reads from the build.lst files in all modules and calls dmake for every directory.

'''parallelism on the global level'''

For parallelism on the global level, you have to run build from <tt>$SRC_ROOT>/instsetoo_native</tt> with the <tt>-P<number></tt> switch, for example:
<pre>
build -P2
</pre>

This takes build how many dmake processes it is allowd to start in parallel.

'''parallelism on the directory level'''

export MAXPROCESS=<numer or processes>

This tells dmake how many targets it is allowed to build in parallel. When you don't use build.pl but build a single directory (single makefile), you can achieve the same with

<pre>
dmake -P2
</pre>

'''combining both levels'''

If you want to have parallelism on both levels, you can call

<pre>
build -P2 -- -P2
</pre>

"--" is a special build.pl parameter that passes every further parameters to the dmake processes it starts.

''' Recommendation '''

Experience tells that using the doubled number of cores in your machine is a good choice, using more threads does not make a big difference, except if the combined option is chosen. So even on single core machines using two threads will speed up the build considerably.

== create prebuilt mozilla ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed).
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <tt>moz</tt> module from the mozilla sources
* use <tt>--enable-build-mozilla</tt> when running configure and put the mozilla-source tarball to <tt>moz/download</tt>
* in <tt>moz</tt> run <tt>dmake zip</tt> to create the zip files
* you'll find the zips in <tt>{platform}.pro/zipped</tt>

Copy them to a location of your liking.
Now instead of using <tt>--enable-build-mozilla</tt>, use <tt>--disable-build-mozilla</tt> and copy the zips you created or downloaded to <tt>moz/zipped</tt> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla).

= See Also =
{{Template:Documentation/Note|For more information on building OOo on Windows see:
* [[Building on Windows (older releases)]]
* [[CPAN_install| Perl modules installation with CPAN]]
* [http://tools.openoffice.org/dev_docs/build_windows_tcsh.html Documentation on tools.openoffice.org]
* [http://website.openoffice.org/support/en/howtos/1.html#1 Documentation on website.openoffice.org]}}

----
<references/>

{{PDL1}}

Documentation/Building Guide/Building on Windows with MinGW

2010-01-11T11:47:10Z

Tono: Added the reason for MinGW build

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}

{{DISPLAYTITLE:Building on Windows with MinGW}}
[[Category:Windows]]
{{Documentation/DraftPage}}

__TOC__

= Overview =

{{Template:Documentation/Windows| This document explains how to build the OpenOffice.org source code on Windows systems with MinGW compiler and linker.}}

== what is MinGW? ==
MinGW stands for Minimalist’s GNU for Windows. It is a set of firee, open source software including compiler, linker,shell environment and other useful tools for developing software. MinGW is intended to support developing software to work on Microsoft 32-bit Windows with minimal support of external libraries. The MinGW community is distributing the g++ compiler from gcc (GNU compiler collection) and GNU ld linker for Windows 32-bit executables in GNU binutils, which is a set of tools to manipulate binary object and executable files.

== the reason why MinGW build is being maintained ==
Please note the official releases of OpenOffice.org for Windows are built using tools from Microsoft. The build with MinGW compiler and linker is being maintained for checking the code portability and keeping the alternative to Microsoft tools. Microsoft compiler does not complain at some codes violating C++ standard and although Microsoft is supplying Visual Studio Express edition free of charge for the time being, they may stop to do so in the future. And it may make sense to keep OOo to be buildable with open source tools.

== Cygwin ==
For building OpenOffice.org Cygwin is needed, a Windows program that emulates a complete Unix command line environment. To use this document you need to be familiar with a command line, but you need not to be a UNIX shell wizard.

{{Template:Documentation/Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}

{{Template:Documentation/Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
{{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.}}

== Cygwin compiler v. s. MinGW compiler ==
Cygwin also includes C++ compiler and linker in its distribution as well as headers and libraries of MinGW. Specifying -mno-cygwin command line switch, the tools can generate the same object code to MinGW compiler. However, as the tools use Cygwin system call to invoke sub programs, the process to build OpenOffice.org with Cygwin’s compiler and linker is a bit slower and more unstable than that with “pure” MinGW tools on Cygwin shell.
== versions and problems in compiler and linker ==
The version of the official release of gcc from MinGW is gcc-3.4.5 for version 3 series and gcc-4.4.0 for version 4 series. 4.4.0 is the first official release of version 4 series and older versions in version 4 series were all experimental. Cygwin includes gcc-3.4.4 and experimental 4.3.2.
Compilers of version 3 series have several problems to build OOo and needs patches. You can get the patched binaries of core C compiler and C++ compiler at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Available version is only 3.4.4. The source patch is also available there. You can get the patched compilers equivalent to them in Cygwin distribution. You have to get core C compiler, C++ compiler and the MinGW libraries for both C and C++ at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Please note that you have to run the postinstall command in /etc/postinstall directory after extracting the distribution of both of the MinGW libraries for C on Cygwin and that for C++ under root directory in Cygwin command prompt.
Compilers of version 4 series have no serious problem to build OOo but the standard C++ library distribution included in the official release of gcc-4.4.0 is only partial and needs to be rebuilt using a Cygwin shell script.
Gcc version 4 emits better code and useful warning messages. However, you should concern licence agreements of dlls. MinGW gcc compiler has restriction to use dynamic linking of the two library libgcc and libstdc++ for proper exception handling and the dlls will be included in the installation set you will build. In the meantime the licence agreements of these dlls have a rather strict term to follow if you redistribute them.
The version of the official release of binutils from both MinGW and Cygwin is 2.19.18 and ld linker has problems to build OOo. The patched binaries and sources are available at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net].
== w32api and MinGW runtime library ==
The set of libraries and headers to let code to use Windows API is distributed as w32api. The version 3.13 is required for building OOo. Some new APIs and constant definitions that are not officially published from Microsoft are not included and you have to use files in Microsoft SDK with smalll patches. MinGW runtime library of version 3.16 is required as well to enable multithreading and fix some C functions. MinGW tools are intended to use Microsoft C runtime library that is always installed in Windows system but some bugs are fixed in MinGW runtime library.
= Requirements =
== hardware requirements ==

* 1 or more reasonable fast CPUs (x-way CPU recommended)
* 1 GB RAM (2 GB recommended)
* 10 GB free disk space (20 GB when debugging)

== software requirements ==
* Windows XP/Vista

The following table is placed here, so you can come back to it easily, when you want to use a link. The items are explained below. Here's the list of files to download (with links) and the locations in the source tree where you must put them:

{| class="prettytable" border="1" width="100%"
|-
! Where to get
! Place in
|-
| Cygwin: [http://www.cygwin.com Cygwin Toolkit with (dll version 1.5.10) or later]
| (default)
|-
| Either of
“pure” gcc 3 series tools including patched “pure” MingW gcc 3 compiler and patched binutils: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools gcc-core-3.4.4-20050522-1-ooopatched.tar.gz gcc-g++-3.4.4-20050522-1-ooopatched.tar.gz binutils-2.19.1-ooopatched.tar.gz] and w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

“pure” gcc 4 series tools including patched binutils and the library rebuilding script: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools binutils-2.19.1-ooopatched.tar.gz gcc-core-g++-4.4.0-install.sh] and MingW gcc 4 compiler, w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ gcc-core-4.4.0-mingw32-bin.tar.gz gcc-core-4.4.0-mingw32-dll.tar.gz gcc-c++-4.4.0-mingw32-bin.tar.gz gcc-c++-4.4.0-mingw32-dll.tar.gz gmp-4.2.4-mingw32-dll.tar.gz mpfr-2.4.1-mingw32-dll.tar.gz pthreads-w32-2.8.0-mingw32-dll.tar.gz w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

Cygwin tools including patched Cygwin gcc 3 compiler and patched binutils (w32api and MinGW runtime for Cygwin compiler/linker are included in Cygwin distribution): [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools/cygwin gcc-core-3.4.4-3ooopatched.tar.bz2 gcc-g++-3.4.4-3ooopatched.tar.bz2 gcc-mingw-core-20050522-ooopatched-1.tar.bz2 gcc-mingw-g++-20050522-ooopatched-1.tar.bz2 binutils-20080624-2-ooopatched.tar.bz2]
| (default)
|-
| Java: [http://java.sun.com/javase/6/ JDK 1.6] for DEV300 milestones >= m37 and all OOo310 versions (older milestones will fail in the hsqldb module)
| (default)
|-
| [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008].<ref name="Foot1">{{Template:Documentation/Note|This also supported on Vista. This is either a DVD image or a net installer. You can either mount the DVD with a suitable tool, burn it do a DVD or use tools like winrar that can extract files from ISO files directly. You don't need to install samples or documentation (saves a lot of disk space). It will also install the .NET Framework 3.5 SDK.
It might be best to install the Windows SDK into the default directory, and if not that into one without capital letters in the path. I used D:\Dev\Win_SDK\ and received some linking errors in the Python module (see {{Bug|88568}}).}}</ref>
|
|-
| [http://www.microsoft.com/downloads/details.aspx?familyid=6A63AB9C-DF12-4D41-933C-BE590FEAA05A&displaylang=en GDI+ Redistributable] (Genuine Windows Validation required)
| external/gdiplus
|-
| Only for OOo2.x but due to {{Bug|88652}} in configure still needed for 3.x: [http://download.microsoft.com/download/b/7/5/b75eace3-00e2-4aa0-9a6f-0b6882c71642/unicows.exe unicows.dll from (Microsoft Layer for Unicode)]<ref name="Foot2">{{Template:Documentation/Note|unicows.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/unicows. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
| external/unicows
|-
| [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CD1FC4B2-0885-47F4-AF45-7FD5E14DB6C0 dbghelp.dll]<ref name="Foot3">{{Template:Documentation/Note|dbghelp.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/dbghelp. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>

| external/dbghelp
|-
| [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/NT45/EN-US/InstMsiW.exe instmsiw.exe] and [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/W9XMe/EN-US/InstMsiA.exe instmsia.exe]
| external/msi
|-
| [http://archive.apache.org/dist/ant/binaries Apache Ant (version 1.6.5 or later)]
| (default)
|-
| either of [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_moz Mozilla binary distribution] for milestone <= DEV300_m52 or [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_seamonkey Seamonkey] for milestone >= DEV300_m53

| moz/zipped
|-
| optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)]<ref name="Foot5">{{Template:Documentation/Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}

{{Template:Documentation/Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}</ref>
|
|-
| optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK]<ref name="Foot6">{{Template:Documentation/Note|If you don't want to download it you can disable DirectX support in the configuration step (<code>--disable-directx</code>).}}

{{Template:Documentation/Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}

{{Template:Documentation/Caution|Do not use a DirectX10 SDK!}}</ref>
|
|-
| optional: [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild]
|
|}
=== adding required files to the build tree ===

{{Template:Documentation/Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}

{{Template:Documentation/Note|OOo uses some Mozilla libraries. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}

= Installation and Preparation of Build Tools =
== setting up cygwin ==

Go to http://www.cygwin.com/ and download and install the current version.
{{Template:Documentation/Caution|Make sure that you keep the filetype set to “Unix/binary”.}}

=== required additional packages ===
Cygwin consists of some basic and a lot of optional packages. As building OOo needs some of these optional packages you have to select them in the installer.
Here's a complete list of the needed packages:
* Category Archive:
** cabextract
** unzip
** zip
* Category Devel :
** autoconf
** bison
** flex
** gcc-g++
** gperf
** make
** openssl-devel (only needed for perl modules for CWS tooling, see below)
** pkgconfig
** cvs (for 2.x code line and 3.0 code line)
** subversion (for 3.x code line, minimum version 1.5.5)
* Category Libs
** openssl
* Category Net
** openssh
** ncftp
** rsync
* Category Perl
** perl
* Category Shells
** rxvt
* Category Utils
** file
** patch
** gnupg
* Category Web
** lynx
** wget
{{Template:Documentation/Caution|You have to exclude the package rebase in Category Base if you use Cygwin compiler for OOo build.}}
{{Template:Documentation/Note|Unfortunately the list of packages mentioned at http://website.openoffice.org/support/en/howtos/1.html#1 is incomplete, some more are listed at http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#BuildRequirements .}}

{{Template:Documentation/Note|The installer will automatically check and download some more packages needed by thosed listed here. The whole process takes roughly 20 minutes.}}

=== breaking links to executables ===
Within the Cygwin Toolkit, some executables might be symlinks: awk.exe and gunzip.exe, tar.exe (in older releases only). This can lead to a break of the build later, and the symlinks should be replaced by copies of the command they link to.

To check this, execute:

ls -l /bin/awk.exe

whether e.g. awk.exe is a symlink. In version 1.5.24-2 awk.exe is a link to gawk.exe. The shell will show this by putting out “awk.exe -> gawk.exe”. In this case gawk.exe must be copied to awk.exe by executing:

cd /bin
rm awk.exe
cp gawk.exe awk.exe

In case you overlook something here or you have a newer Cygwin version with additional symlinks not mentioned here it's not a problem. You will get a helpful error message about an existing link in the configuration step (configure) later. The message will tell you which link you have to remove and you can do it following the advice given above for the awk.exe/gawk.exe pair.

=== installing additional perl modules in cygwin ===
As explained some perl modules must be installed with CPAN. The necessary command in the cygwin shell is

perl -MCPAN -e shell

If this command is executed the first time CPAN will ask for configuration. Choose autoconfiguration.

{{Template:Documentation/Caution|Please note that CPAN is not able to deal with usernames containing spaces. To work around this fact, when CPAN asks you to specify the ''CPAN build and cache directory'', change the default suggestion to <tt>/cpan</tt>.}}

At the end the CPAN shell appeared and is ready to accept commands for installations. Each module is installed by typing <code>install $MODULENAME</code>. The modules that must be installed are:

* Archive::Zip
* XML::Parser (though it seems that this is already installed; doesn't hurt to do it)
* URI
* LWP::UserAgent
* Crypt::SSLeay
* SOAP::Lite

CPAN will detect if a selected module depends on other modules and it will offer to download them also. As explained please just confirm this.

{{Template:Documentation/Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}

{{Template:Documentation/Caution|I got an error message from CPAN somewhat like the following:
<pre>C:\cygwin\bin\perl.exe: *** unable to remap C:\cygwin\bin\cygiconv-2.dll to same
address as parent(0x7C0000) != 0x7D0000</pre>
To fix this, I had to exit the Cygwin shell, run cmd.exe, then type "c:\cygwin\bin\ash.exe" to start the minimal shell, then type <code>/bin/rebaseall</code>. Then CPAN worked when I ran it again.}}

{{Template:Documentation/Caution| I got another error when cygwin was performing <tt>make install</tt>:
<pre>ERROR: Can't create '/usr/bin'; Do not have write permissions on '/usr/bin'</pre>
I can actually write to /usr/bin; however when I do <tt>ls -ld /usr/bin</tt>, cygwin reports no write permission; and <tt>chmod u+w /usr/bin</tt> gives <tt>Permission denied</tt>. This causes the install process to fail when it checks permissions. As a kludge, I installed vim, and edited line 368 of /usr/lib/perl5/5.10/ExtUtils/Install.pm, replacing this:
<pre>return -w $dir;</pre>
with this:
<pre>return 1;</pre>
which allowed installation to proceed.}}

== installing compiler and binutils ==
=== installing “pure” MinGW gcc version 3 series compiler and binutils ===
To install “pure” MinGW gcc version 3 series compiler and binutils, you have to create a unique directory first, say <tt>c:/mingw</tt>. All you have to do is to extract all tarballs here.

tar -C c:/mingw -xvzpf xxx.tar.gz

=== installing “pure” MinGW gcc version 4 series compiler and binutils ===
To install “pure” MinGW gcc version 4 series compiler and binutils, you have to choose a unique directory name, say <tt>c:/mingw</tt>, put everything you downloaded in one working directory and invoke the following command in the directory.

./gcc-core-g++-4.4.0-install.sh c:/mingw

=== installing Cygwin gcc version 3 series compiler and binutils ===
You have to extract all tarballs in root directory.

tar -C / -xvjpf xxx.tar.gz

The tarballs for gcc-mingw-gcc and gcc-mingw-g++ include postinstall scripts. You have to run them to complete installation.

/etc/postinstall/gcc-mingw-core.sh
/etc/postinstall/gcc-mingw-g++.sh

= Full Builds =
== configure ==
Finally the <code>configure</code> tool is used to create the environment. It checks that all software, hardware, and system requirements for the build are satisfied, and creates configuration files called winmingw.set (for tcsh) and winmingw.set.sh (for bash) that are used to set all necessary build environment variables. Before running configure, make sure that all needed programs are in the system path or start configure with the appropriate command line switches. If configure detects a problem it will stop and give you a useful hint how to fix it.

You will find the <code>configure</code> script in <code>$SRC_ROOT</code>. The resulting configuration files are created there too.

==== sample configure calls ====

./configure \
--with-mingwin=yes \
--disable-directx \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-use-shell=bash
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS

./configure \
--with-mingwin=yes \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-use-shell=bash
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS \
--enable-crashdump \
--enable-symbols=SMALL \
--enable-vba \
--enable-minimizer \
--enable-presenter-console \
--enable-pdfimport \
--enable-wiki-publisher \
--enable-report-builder \
--enable-cairo

==== configure settings tips ====
{{Template:Documentation/Caution|Make sure that the <code>PATH</code> variable in your cygwin shell does not contain any blanks and quotes.}}
{{Template:Documentation/Caution|Paths might have problems with spaces. Install requirements into paths without them. Alternatively, feel free to install the various packages using the default path containing spaces and then use the mixed short path for the configure stage. The mixed short path can be obtained using Cygwin's cygpath tool, eg:
<pre>$ cygpath -m -s "c:\Program Files\Microsoft SDKs"
c:/PROGRA~1/MI2578~1</pre>
The <code>with-psdk-home</code> setting needs a case-sensitive path name. I recommend to use case-sensitive usage in all cases - it's good to get used to case sensitivity if you are going to work with Cygwin.}}
{{Template:Documentation/Caution|Beware of using <code>/c/</code> instead of <code>/cygdrive/c/</code>.}}
{{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
{{Template:Documentation/Note|Paths to dependencies might be different for your installation. The paths containing "msvc" and "msdk" should be self-explanatory.}}
{{Template:Documentation/Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
<pre>./configure --help</pre>}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <code>WINDOWS_VISTA_PSDK</code> to be set <code>TRUE</code>. This is important if <code>configure</code> fails to detect the Windows platform SDK version correctly. The detection failure results from the way that <code>configure</code> searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <code>DISABLE_ATL</code>, <code>DISABLE_ACTIVEX</code>: all have to be set <code>TRUE</code>. If you want to build the OOo ActiveX control, OLE automation and native Windows OLE support, you have to copy atl headers from old release of Microsoft Platform SDK.}}
{{Template:Documentation/Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <code>--disable-directx</code> as shown above. Otherwise you have to provide the path to the SDK in <code>--with-directx-home</code>.}}
{{Template:Documentation/Tip|OOo uses some Mozilla components. Disabling the Mozilla components completely with <code>--disable-mozilla</code> currently might not work due to a bug in the module dependencies.}}
{{Template:Documentation/Tip|If you experiment with the newest sources, mind that it can happen sometimes that <code>configure.in</code> was updated, but it was forgotten to update configure too. The configure script itself is created from <code>configure.in</code> using the <code>autoreconf</code> command. The perl script <code>set_soenv</code> is created when you run configure from <code>set_soenv.in</code>.}}
{{Template:Documentation/Tip|csc.exe comes from the <code>c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</code> directory, you might need <code>--with-csc-path</code>.}}
{{Template:Documentation/Tip|If you fail to getting together a working installation of Cygwin, one possibility is to use a known-to-work combination of Cygwin packages, i.e. a direct copy of some other user's Cygwin tree. [[User:TorLillqvist]] has such a tree (from late 2006) zipped up at http://download.go-oo.org/tstnvl/tml/tml-cygwin.zip . Don't hesitate to ask for advice if necessary.}}

== bootstrap ==
After running configure you must create the dmake make utility that is needed for the build of OpenOffice.org. This done from the SRC_ROOT directory by calling

./bootstrap

== setting the environment ==

When the configure script has been run successfully a file <code>winmingw.Set.sh</code> was created<ref name="Foot7">{{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <code>winmingw.Set</code> instead:
<pre> source winmingw.Set
rehash</pre>
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.}}</ref>. Do this:

source winmingw.Set.sh

to set up the environment for the build.

== starting the build ==
Build the software by typing the following in <code>$SRC_ROOT</code> <ref name="Foot8">{{Template:Documentation/Note|You can also run:
<pre>make</pre>
but GNU/make will just start dmake. You can also run the following in the <code>instetoo_native</code> module:
<pre>build --all</pre>
For details run:
<pre>build --help</pre>}}</ref>:
dmake

The building procedure will take at least an hour (on a 3 GHz Quad-Core with 8GB RAM).

There are some special things in the way how OOo builds its modules. Every module has an “output” folder (with some subfolders for the different kinds of generated output) that is created the first time a build is done in the module. The name of this folder is “wntgcci.pro” (for the meaning of the "pro" extension see below). After a successful build of a module some of the generated files are copied to the output folder of the “solver” module by executing a tool called “deliver” (this is automatically called by build --all for each of the modules). Other modules will take these “delivered” files (header files, libraries etc.) to resolve their dependencies. The content of the solver module will also be used to pack the installation sets in the final step.

{{Template:Documentation/Tip|Using some not quite latest cygwin releases (1.5.18/1.5.19) can lead to tcsh freezing in places - the build will appear to hang. You can fix this by running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
<pre>ls /proc/*/fd</pre>
to "unhang" the process. See {{Bug|51560}} for more info...}}

= Partial Builds =
There are two ways to do partial builds:
* compatible
* incompatible
Only do compatible partial builds if you know exactly what you are doing.
{{Documentation/Note|For more information, see [[Compatible Builds]].}}
== rebuilding from a module (incompatible build) ==

If you decide to change 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

== rebuilding a module (compatible build) ==

To rebuild a module you can delete all output directories with, rebuild and redeliver into the solver with:

cd $MODULE
build --from $MODULE --prepare
build && deliver

A simple <code>build</code> in <code>$SRC_ROOT/instsetoo_native</code> will recreate the installation sets, provided all other modules have already been build. <ref name="Foot9">{{Documentation/Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}</ref>

= 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 debug=true --from $MODULE

Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.

{{Template:Documentation/Tip|For details, see [[Windows Debugging]].}}
= Finding the Installation Sets =
After a successful build you will find the OOo installation set in

instsetoo_native/wntmscixx.pro/OpenOffice/msi/Install/en-US

“instsetoo_native” is the module that packs the installation set.

{{Documentation/Tip|If you already have a version of OOo installed you can install your freshly built version in parallel by installing it with setup /a that just unpacks all files without any system registration.}}

= Tips And Tricks =
== ccache ==
For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers
== dependencies ==

'''nodep'''

If you set the environment variable <code>nodep</code> to <code>TRUE</code>, then dependendy information files are not created - the build finishes faster.

{{Template:Documentation/Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}

'''NO_HIDS'''

Similar to the <code>nodep</code> variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile (directory) level, the other one on the global level. The two levels of parallelism result from the two-step build procedure in the OOo build environment. The build script runs through all the directories it reads from the build.lst files in all modules and calls dmake for every directory.

'''parallelism on the global level'''

For parallelism on the global level, you have to run build from <code>$SRC_ROOT>/instsetoo_native</code> with the <code>-P<number></code> switch, for example:
<pre>
build -P2
</pre>

This takes build how many dmake processes it is allowd to start in parallel.

'''parallelism on the directory level'''

export MAXPROCESS=<numer or processes>

This tells dmake how many targets it is allowed to build in parallel. When you don't use build.pl but build a single directory (single makefile), you can achieve the same with

<pre>
dmake -P2
</pre>

'''combining both levels'''

If you want to have parallelism on both levels, you can call

<pre>
build -P2 -- -P2
</pre>

"--" is a special build.pl parameter that passes every further parameters to the dmake processes it starts.

''' Recommendation '''

Experience tells that using the doubled number of cores in your machine is a good choice, using more threads does not make a big difference, except if the combined option is chosen. So even on single core machines using two threads will speed up the build considerably.

== create prebuilt mozilla ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed).
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources
* use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{platform}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla).

= See Also =
{{Template:Documentation/Note|For more information on building OOo on Windows see:
* [[Building on Windows (older releases)]]
* [[CPAN_install| Perl modules installation with CPAN]]
* [http://tools.openoffice.org/dev_docs/build_windows_tcsh.html Documentation on tools.openoffice.org]
* [http://website.openoffice.org/support/en/howtos/1.html#1 Documentation on website.openoffice.org]}}

----
<references/>

{{PDL1}}

Talk:Documentation/Building Guide/Building on Windows with MinGW

2009-10-04T09:53:10Z

Tono: /* Answer to TJ */ new section

== Light Copy Editing complete ==

I did a little work on several sections, just minor spelling and grammar fixes.

Points of further interest:
* Added template call to DraftPage. You can remove it whenever you like.
* Section 1.4, "versions and problems in compiler and linker", needs work. Regrettably, I am not sure enough of the information to rearrange it with any degree of confidence. It needs to be in several paragraphs, with possibly some short bullet lists.

Question: do you intend this page as a replacement for the current "Building on Windows", or a supplement to it?

Let me know when you want to add this to the TOC (with a "(draft)" note?) --[[User:TJFrazier|TJ]] 01:45, 28 September 2009 (UTC)

== Answer to TJ ==

I do not want this page to substitute the Windows build guide.
MinGW port is a technical alternative to Microsoft Visual C++ but it is not intended to be a complete substitute.
So the build guide for MinGW should be a supplement to Windows build guide.

As to Section 1.4, I would like to have more comments from experts.

I would like to get the document to be reviewed by many people.
So, I think it should be in TOC right away.

Documentation/Building Guide/Building on Windows with MinGW

2009-09-27T09:09:57Z

Tono: Created page with '{{Documentation/Building Guide TOC |ShowNextPage=none |ShowPrevPage=none }} {{DISPLAYTITLE:Building on Windows with MinGW}} Category:Windows __TOC__ = Overview = {{Templa…'

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}

{{DISPLAYTITLE:Building on Windows with MinGW}}
[[Category:Windows]]

__TOC__

= Overview =

{{Template:Documentation/Windows| This document explains how to build the OpenOffice.org source code on Windows systems with MinGW compiler and linker.}}

== what is MinGW? ==
MinGW stands for Minimalist’s GNU for Windows. It is a set of firee, open source software including compiler, linker,shell environment and other useful tools for developing software. MinGW is intended to support developing software to work on Microsoft 32-bit Windows with minimal support of external library. MinGW community is distributing g++ compiler from gcc (GNU compiler collection) and GNU ld linnker for Windows 32-bit executables in GNU binutils, which is a set of tools to manipulate binary object and executable files.
== Cygwin ==
For building OpenOffice.org Cygwin is needed, a Windows program that emulates a complete Unix command line environment. To use this document you need to be familiar with a command line, but you need not to be a UNIX shell wizard.

{{Template:Documentation/Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}

{{Template:Documentation/Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
{{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.}}

== Cygwin compiler v. s. MinGW compiler ==
Cygwin also includes C++ compiler and linker in its distribution as well as headers and libraries of MinGW. Specifying -mno-cygwin command line switch, the tools can generate the same object code to MinGW compiler. However, as the tools use Cygwin system call to invoke sub programs, the process to build OpenOffice.org with Cygwin’s compiler and linker is a bit slower and more unstable than that with “pure” MinGW tools on Cygwin shell.
== versions and problems in compiler and linker ==
The version of the official release of gcc from MinGW is gcc-3.4.5 for version 3 series and gcc-4.4.0 for version 4 series. 4.4.0 is the first official release of version 4 series and older versions in version 4 series were all experimental. Cygwin includes gcc-3.4.4 and experimental 4.3.2.
Compilers of version 3 series have several problems to build OOo and needs patches. You can get the patched binaries of core C compiler and C++ compiler at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Available version is only 3.4.4. The source patch is also available there. You can get the patched compilers equivalent to them in Cygwin distribution. You have to get core C compiler, C++ compiler and the MinGW libraries for both C and C++ at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net]. Please note that you have to run the postinstall command in /etc/postinstall directory after extracting the distribution of both of the MinGW libraries for C on Cygwin and that for C++ under root directory in Cygwin command prompt.
Compilers of version 4 series have no serious problem to build OOo but the standard C++ library distribution included in the official release of gcc-4.4.0 is only partial and needs to be rebuilt using a Cygwin shell script.
Gcc version 4 emits better code and useful warning messages. However, you should concern licence agreements of dlls. MinGW gcc compiler has restriction to use dynamic linking of the two library libgcc and libstdc++ for proper exception handling and the dlls will be included in the installation set you will build. In the meantime the licence agreements of these dlls have a rather strict term to follow if you redistribute them.
The version of the official release of binutils from both MinGW and Cygwin is 2.19.18 and ld linker has problems to build OOo. The patched binaries and sources are available at [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW ooopackages.good-day.net].
== w32api and MinGW runtime library ==
The set of libraries and headers to let code to use Windows API is distributed as w32api. The version 3.13 is required for building OOo. Some new APIs and constant definitions that are not officially published from Microsoft are not included and you have to use files in Microsoft SDK with smalll patches. MinGW runtime library of version 3.16 is required as well to enable multithreading and fix some C functions. MinGW tools are intended to use Microsoft C runtime library that is always installed in Windows system but some bugs are fixed in MinGW runtime library.
= Requirements =
== hardware requirements ==

* 1 or more reasonable fast CPUs (x-way CPU recommended)
* 1 GB RAM (2 GB recommended)
* 10 GB free disk space (20 GB when debugging)

== software requirements ==
* Windows XP/Vista

The following table is placed here, so you can come back to it easily, when you want to use a link. The items are explained below. Here's the list of files to download (with links) and the locations in the source tree where you must put them:

{| class="prettytable" border="1" width="100%"
|-
! Where to get
! Place in
|-
| Cygwin: [http://www.cygwin.com Cygwin Toolkit with (dll version 1.5.10) or later]
| (default)
|-
| Either of
“pure” gcc 3 series tools including patched “pure” MingW gcc 3 compiler and patched binutils: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools gcc-core-3.4.4-20050522-1-ooopatched.tar.gz gcc-g++-3.4.4-20050522-1-ooopatched.tar.gz binutils-2.19.1-ooopatched.tar.gz] and w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

“pure” gcc 4 series tools including patched binutils and the library rebuilding script: [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools binutils-2.19.1-ooopatched.tar.gz gcc-core-g++-4.4.0-install.sh] and MingW gcc 4 compiler, w32api and MinGW runtime: [http://sourceforge.net/projects/mingw/files/ gcc-core-4.4.0-mingw32-bin.tar.gz gcc-core-4.4.0-mingw32-dll.tar.gz gcc-c++-4.4.0-mingw32-bin.tar.gz gcc-c++-4.4.0-mingw32-dll.tar.gz gmp-4.2.4-mingw32-dll.tar.gz mpfr-2.4.1-mingw32-dll.tar.gz pthreads-w32-2.8.0-mingw32-dll.tar.gz w32api-3.13-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dev.tar.gz mingwrt-3.16-mingw32-dll.tar.gz] or

Cygwin tools including patched Cygwin gcc 3 compiler and patched binutils (w32api and MinGW runtime for Cygwin compiler/linker are included in Cygwin distribution): [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/tools/cygwin gcc-core-3.4.4-3ooopatched.tar.bz2 gcc-g++-3.4.4-3ooopatched.tar.bz2 gcc-mingw-core-20050522-ooopatched-1.tar.bz2 gcc-mingw-g++-20050522-ooopatched-1.tar.bz2 binutils-20080624-2-ooopatched.tar.bz2]
| (default)
|-
| Java: [http://java.sun.com/javase/6/ JDK 1.6] for DEV300 milestones >= m37 and all OOo310 versions (older milestones will fail in the hsqldb module)
| (default)
|-
| [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008]. [[#Foot1|1]]
|
|-
| [http://www.microsoft.com/downloads/details.aspx?familyid=6A63AB9C-DF12-4D41-933C-BE590FEAA05A&displaylang=en GDI+ Redistributable] (Genuine Windows Validation required)
| external/gdiplus
|-
| Only for OOo2.x but due to {{Bug|88652}} in configure still needed for 3.x: [http://download.microsoft.com/download/b/7/5/b75eace3-00e2-4aa0-9a6f-0b6882c71642/unicows.exe unicows.dll from (Microsoft Layer for Unicode)] [[#Foot2|2]]
| external/unicows
|-
| [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CD1FC4B2-0885-47F4-AF45-7FD5E14DB6C0 dbghelp.dll] [[#Foot3|3]]
| external/dbghelp
|-
| [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/NT45/EN-US/InstMsiW.exe instmsiw.exe] and [http://download.microsoft.com/download/WindowsInstaller/Install/2.0/W9XMe/EN-US/InstMsiA.exe instmsia.exe]
| external/msi
|-
| [http://archive.apache.org/dist/ant/binaries Apache Ant (version 1.6.5 or later)]
| (default)
|-
| either of [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_moz Mozilla binary distribution] for milestone <= DEV300_m52 or [ftp://ooopackages.good-day.net/pub/OpenOffice.org/Windows/MinGW/misc/prebuild_seamonkey Seamonkey] for milestone >= DEV300_m53

| moz/zipped
|-
| optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)][[#Foot5|5]]
|
|-
| optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK][[#Foot6|6]]
|
|-
| optional: [http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.4.exe MozillaBuild]
|
|}
=== adding required files to the build tree ===

{{Template:Documentation/Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}

{{Template:Documentation/Note|OOo uses some Mozilla libraries. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}

= Installation and Preparation of Build Tools =
== setting up cygwin ==

Go to http://www.cygwin.com/ and download and install the current version.
{{Template:Documentation/Caution|Make sure that you keep the filetype set to “Unix/binary”.}}

=== required additional packages ===
Cygwin consists of some basic and a lot of optional packages. As building OOo needs some of these optional packages you have to select them in the installer.
Here's a complete list of the needed packages:
* Category Archive:
** unzip
** zip
* Category Devel :
** autoconf
** bison
** flex
** gcc-g++
** gperf
** make
** openssl-devel (only needed for perl modules for CWS tooling, see below)
** cvs (for 2.x code line and 3.0 code line)
** subversion (for 3.x code line, minimum version 1.5.5)
* Category Libs
** openssl
* Category Net
** openssh
** ncftp
* Category Perl
** perl
* Category Shells
** rxvt
* Category Utils
** file
** patch
** gnupg
* Category Web
** lynx
** wget
{{Template:Documentation/Caution|You have to exclude the package rebase in Category Base if you use Cygwin compiler for OOo build.}}
{{Template:Documentation/Note|Unfortunately the list of packages mentioned at http://website.openoffice.org/support/en/howtos/1.html#1 is incomplete, some more are listed at http://tools.openoffice.org/dev_docs/build_windows_tcsh.html#BuildRequirements .}}

{{Template:Documentation/Note|The installer will automatically check and download some more packages needed by thosed listed here. The whole process takes roughly 20 minutes.}}

=== breaking links to executables ===
Within the Cygwin Toolkit, some executables might be symlinks: awk.exe and gunzip.exe, tar.exe (in older releases only). This can lead to a break of the build later, and the symlinks should be replaced by copies of the command they link to.

To check this, execute:

ls -l /bin/awk.exe

whether e.g. awk.exe is a symlink. In version 1.5.24-2 awk.exe is a link to gawk.exe. The shell will show this by putting out “awk.exe -> gawk.exe”. In this case gawk.exe must be copied to awk.exe by executing:

cd /bin
rm awk.exe
cp gawk.exe awk.exe

In case you overlook something here or you have a newer Cygwin version with additional symlinks not mentioned here it's not a problem. You will get a helpful error message about an existing link in the configuration step (configure) later. The message will tell you which link you have to remove and you can do it following the advice given above for the awk.exe/gawk.exe pair.

=== installing additional perl modules in cygwin ===
As explained some perl modules must be installed with CPAN. The necessary command in the cygwin shell is

perl -MCPAN -e shell

If this command is executed the first time CPAN will ask for configuration. Choose autoconfiguration.

{{Template:Documentation/Caution|Please note that CPAN is not able to deal with usernames containing spaces. To work around this fact, when CPAN asks you to specify the ''CPAN build and cache directory'', change the default suggestion to <tt>/cpan</tt>.}}

At the end the CPAN shell appeared and is ready to accept commands for installations. Each module is installed by typing <code>install $MODULENAME</code>. The modules that must be installed are:

* Archive::Zip
* XML::Parser (though it seems that this is already installed; doesn't hurt to do it)
* URI
* LWP::UserAgent
* Crypt::SSLeay
* SOAP::Lite

CPAN will detect if a selected module depends on other modules and it will offer to download them also. As explained please just confirm this.

{{Template:Documentation/Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}

{{Template:Documentation/Caution|I got an error message from CPAN somewhat like the following:
<pre>C:\cygwin\bin\perl.exe: *** unable to remap C:\cygwin\bin\cygiconv-2.dll to same
address as parent(0x7C0000) != 0x7D0000</pre>
To fix this, I had to exit the Cygwin shell, run cmd.exe, then type "c:\cygwin\bin\ash.exe" to start the minimal shell, then type <code>/bin/rebaseall</code>. Then CPAN worked when I ran it again.}}

{{Template:Documentation/Caution| I got another error when cygwin was performing <tt>make install</tt>:
<pre>ERROR: Can't create '/usr/bin'; Do not have write permissions on '/usr/bin'</pre>
I can actually write to /usr/bin; however when I do <tt>ls -ld /usr/bin</tt>, cygwin reports no write permission; and <tt>chmod u+w /usr/bin</tt> gives <tt>Permission denied</tt>. This causes the install process to fail when it checks permissions. As a kludge, I installed vim, and edited line 368 of /usr/lib/perl5/5.10/ExtUtils/Install.pm, replacing this:
<pre>return -w $dir;</pre>
with this:
<pre>return 1;</pre>
which allowed installation to proceed.}}

== installing compiler and binutils ==
=== installing “pure” MinGW gcc version 3 series compiler and binutils ===
To install “pure” MinGW gcc version 3 series compiler and binutils, you have to create an unique dorectory first, say c:/mingw. All you have to do is to extract all tarballs here.

tar -C c:/mingw -xvzpf xxx.tar.gz

=== installing “pure” MinGW gcc version 4 series compiler and binutils ===
To install “pure” MinGW gcc version 4 series compiler and binutils, you have to choose an unique dorectory name, say c:/mingw, put everything you downloaded in one working directory and invoke the following command in the directory.

./gcc-core-g++-4.4.0-install.sh c:/mingw

=== installing Cygwin gcc version 3 series compiler and binutils ===
You have to extract all tarballs in root directory.

tar -C / -xvjpf xxx.tar.gz

The tarballs for gcc-mingw-gcc and gcc-mingw-g++ include postinstall scripts. You have to run them to complete installation.

/etc/postinstall/gcc-mingw-core.sh
/etc/postinstall/gcc-mingw-g++.sh

= Full Builds =
== configure ==
Finally the <code>configure</code> tool is used to create the environment. It checks that all software, hardware, and system requirements for the build are satisfied, and creates configuration files called winmingw.set (for tcsh) and winmingw.set.sh (for bash) that are used to set all necessary build environment variables. Before running configure, make sure that all needed programs are in the system path or start configure with the appropriate command line switches. If configure detects a problem it will stop and give you a useful hint how to fix it.

You will find the <code>configure</code> script in <code>$SRC_ROOT</code>. The resulting configuration files are created there too.

==== sample configure calls ====

./configure \
--with-mingwin=yes \
--disable-directx \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-use-shell=bash
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS

./configure \
--with-mingwin=yes \
--disable-activex \
--disable-atl \
--disable-build-mozilla \
--with-frame-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-psdk-home="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1" \
--with-midl-path="/cygdrive/c/PROGRA~1/MI2578~1/Windows/v6.1/Bin" \
--with-jdk-home="/cygdrive/c/PROGRA~1/j2sdk1.4.2_11" \
--with-csc-path="/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5" \
--with-ant-home=/ant \
--with-use-shell=bash
--with-mozilla-build=/cygdrive/c/mozilla-build/moztools \
--with-nsis-path=/cygdrive/c/PROGRA~1/NSIS \
--enable-crashdump \
--enable-symbols=SMALL \
--enable-vba \
--enable-minimizer \
--enable-presenter-console \
--enable-pdfimport \
--enable-wiki-publisher \
--enable-report-builder \
--enable-cairo

==== configure settings tips ====
{{Template:Documentation/Caution|Make sure that the <code>PATH</code> variable in your cygwin shell does not contain any blanks and quotes.}}
{{Template:Documentation/Caution|Paths might have problems with spaces. Install requirements into pathes without them. Alternatively, feel free to install the various packages using the default path containing spaces and then use the mixed short path for the configure stage. The mixed short path can be obtained using Cygwin's cygpath tool, eg:
<pre>$ cygpath -m -s "c:\Program Files\Microsoft SDKs"
c:/PROGRA~1/MI2578~1</pre>
The <code>with-psdk-home</code> setting needs a case-sensitive path name. I recommend to use case-sensitive usage in all cases - it's good to get used to case sensitivity if you are going to work with Cygwin.}}
{{Template:Documentation/Caution|Beware of using <code>/c/</code> instead of <code>/cygdrive/c/</code>.}}
{{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
{{Template:Documentation/Note|Paths to dependencies might be different for your installation. The pathes containing "msvc" and "msdk" should be self-explanatory.}}
{{Template:Documentation/Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
<pre>./configure --help</pre>}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <code>WINDOWS_VISTA_PSDK</code> to be set <code>TRUE</code>. This is important if <code>configure</code> fails to detect the Windows platform SDK version correctly. The detection failure results from the way how configure searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winmingw.set.sh for <code>DISABLE_ATL</code>, <code>DISABLE_ACTIVEX</code>: all have to be set <code>TRUE</code>. If you want to build the OOo ActiveX control, OLE automation and native Windows OLE support, you have to copy atl headers from old release of Microsoft Platform SDK.}}
{{Template:Documentation/Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <code>--disable-directx</code> as shown above. Otherwise you have to provide the path to the SDK in <code>--with-directx-home</code>.}}
{{Template:Documentation/Tip|OOo uses some Mozilla components. Disabling the Mozilla components with <code>--disable-mozilla</code> completely currently does might not work due to a bug in the module dependencies.}}
{{Template:Documentation/Tip|If you experiment with the newest sources, mind that it can happen sometimes that <code>configure.in</code> was updated, but it was forgotten to update configure too. The configure script itself is created from <code>configure.in</code> using the <code>autoreconf</code> command. The perl script <code>set_soenv</code> is created when you run configure from <code>set_soenv.in</code>.}}
{{Template:Documentation/Tip|csc.exe comes from the <code>c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</code> directory, you might need <code>--with-csc-path</code>.}}
{{Template:Documentation/Tip|If you fail to getting together a working installation of Cygwin, one possibility is to use a known-to-work combination of Cygwin packages, i.e. a direct copy of some other user's Cygwin tree. [[User:TorLillqvist]] has such a tree (from late 2006) zipped up at http://download.go-oo.org/tstnvl/tml/tml-cygwin.zip . Don't hesitate to ask for advice if necessary.}}

== bootstrap ==
After running configure you must create the dmake make utility that is needed for the build of OpenOffice.org. This done from the SRC_ROOT directory by calling

./bootstrap

== setting the enviroment ==

When the configure script has been run successfully a file <code>winmingw.Set.sh</code> was created[[#Foot7|7]]. Do this:

source winmingw.Set.sh

to set up the enviroment for the build.

== starting the build ==
Build the software by typing the following in <code>$SRC_ROOT</code>[[#Foot8|8]]:
dmake

The building procedure will take at least an hour (on a 3 GHz Quad-Core with 8GB RAM).

There are some special things in the way how OOo builds its modules. Every module has an “output” folder (with some subfolders for the different kinds of generated output) that is created the first time a build is done in the module. The name of this folder is “wntgcci.pro” (for the meaning of the "pro" extension see below). After a successful build of a module some of the generated files are copied to the output folder of the “solver” module by executing a tool called “deliver” (this is automatically called by build --all for each of the modules). Other modules will take these “delivered” files (header files, libraries etc.) to resolve their dependencies. The content of the solver module will also be used to pack the installation sets in the final step.

{{Template:Documentation/Tip|Using some not quite latest cygwin releases (1.5.18/1.5.19) can lead to tcsh freezing in places - the build will appear to hang. You can fix this by running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
<pre>ls /proc/*/fd</pre>
to "unhang" the process. See {{Bug|51560}} for more info...}}

= Partial Builds =
There are two ways to do partial builds:
* compatible
* incompatible
Only do compatible partial builds if you know exactly what you are doing.
{{Documentation/Note|For more information, see [[Compatible Builds]].}}
== rebuilding from a module (incompatible build) ==

If you decide to change 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

== rebuilding a module (compatible build) ==

To rebuild a module you can delete all output directories with, rebuild and redeliver into the solver with:

cd $MODULE
build --from $MODULE --prepare
build && deliver

A simple <code>build</code> in <code>$SRC_ROOT/instsetoo_native</code> will recreate the installation sets, provided all other modules have already been build.[[#Foot9|9]]

= 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 debug=true --from $MODULE

Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.

{{Template:Documentation/Tip|For details, see [[Windows Debugging]].}}
= Finding the Installation Sets =
After a successful build you will find the OOo installation set in

instsetoo_native/wntmscixx.pro/OpenOffice/msi/Install/en-US

“instsetoo_native” is the module that packs the installation set.

{{Documentation/Tip|If you already have a version of OOo installed you can install your freshly built version in parallel by installing it with setup /a that just unpacks all files without any system registration.}}

= Tips And Tricks =
== ccache ==
For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers
== dependencies ==

'''nodep'''

If you set the environment variable <code>nodep</code> to <code>TRUE</code>, then dependendy information files are not created - the build finishes faster.

{{Template:Documentation/Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}

'''NO_HIDS'''

Similar to the <code>nodep</code> variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile (directory) level, the other one on the global level. The two levels of parallelism result from the two-step build procedure in the OOo build environment. The build script runs through all the directories it reads from the build.lst files in all modules and calls dmake for every directory.

'''parallelism on the global level'''

For parallelism on the global level, you have to run build from <code>$SRC_ROOT>/instsetoo_native</code> with the <code>-P<number></code> switch, for example:
<pre>
build -P2
</pre>

This takes build how many dmake processes it is allowd to start in parallel.

'''parallelism on the directory level'''

export MAXPROCESS=<numer or processes>

This tells dmake how many targets it is allowed to build in parallel. When you don't use build.pl but build a single directory (single makefile), you can achieve the same with

<pre>
dmake -P2
</pre>

'''combining both levels'''

If you want to have parallelism on both levels, you can call

<pre>
build -P2 -- -P2
</pre>

"--" is a special build.pl parameter that passes every further parameters to the dmake processes it starts.

''' Recommendation '''

Experience tells that using the doubled number of cores in your machine is a good choice, using more threads does not make a big difference, except if the combined option is chosen. So even on single core machines using two threads will speed up the build considerably.

== create prebuilt mozilla ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed).
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources
* use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{platform}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla).

= See Also =
{{Template:Documentation/Note|For more information on building OOo on Windows see:
* [[Building on Windows (older releases)]]
* [[CPAN_install| Perl modules installation with CPAN]]
* [http://tools.openoffice.org/dev_docs/build_windows_tcsh.html Documentation on tools.openoffice.org]
* [http://website.openoffice.org/support/en/howtos/1.html#1 Documentation on website.openoffice.org]}}

= Footnotes =

1 {{Template:Documentation/Note|This also supported on Vista. This is either a DVD image or a net installer. You can either mount the DVD with a suitable tool, burn it do a DVD or use tools like winrar that can extract files from ISO files directly. You don't need to install samples or documentation (saves a lot of disk space). It will also install the .NET Framework 3.5 SDK.
It might be best to install the Windows SDK into the default directory, and if not that into one without capital letters in the path. I used D:\Dev\Win_SDK\ and received some linking errors in the Python module (see {{Bug|88568}}).}}

2 {{Template:Documentation/Note|unicows.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/unicows. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}

3 {{Template:Documentation/Note|dbghelp.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/dbghelp. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}

4 {{Template:Documentation/Note|You can find these files in your directory c:\program files\common files\merge modules}}

5 {{Template:Documentation/Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}

{{Template:Documentation/Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}

6 {{Template:Documentation/Note|If you don't want to download it you can disable DirectX support in the configuration step (<code>--disable-directx</code>).}}

{{Template:Documentation/Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}

{{Template:Documentation/Caution|Do not use a DirectX10 SDK!}}

7 {{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <code>winmingw.Set</code> instead:
<pre> source winmingw.Set
rehash</pre>
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.}}

8 {{Template:Documentation/Note|You can also run:
<pre>make</pre>
but GNU/make will just start dmake. You can also run the following in the <code>instetoo_native</code> module:
<pre>build --all</pre>
For details run:
<pre>build --help</pre>}}

9 {{Documentation/Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}

{{PDL1}}

DomainDeveloper

2008-06-13T23:44:28Z

Tono: Adding myself

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| class="prettytable sortable"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Gene Anaya|| || ganaya||||||
|-
| Joost Andrae|| X || ja||ja||CL qa, release testing en-US builds and releasing builds||Sun Microsystems
|-
| Eric Bachard|| X || ericb||ericb2|| CL Education, Mac OSX/Linux PPC port ||Education project
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Omer Bar-or|| X || cremlae||cremlae||Mac porting||Google Summer of Code
|-
| Mathias Bauer|| X || mba||||PL Writer, CL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Sun Microsystems
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stephan Bergmann|| X || sb||||CL UDK||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||Rafaella ||PL l10n, Globalization Program Manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||plumbumm||UI||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||PL Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Jinhong Chen || || chainchen || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Xiuzhi Cheng|| X || xzcheng || xiuzhi|| ESC,Xml,ODF|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Quangang Dong|| || donqg || dongqg || Layout || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd|| cd_oo ||PL Framework||Sun Microsystems
|-
| Yunfen Du || X || duyunfen|| dyf|| Base ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-

| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| Bernd Eilers|| X || bei||rfc821||EIS||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| [[User:Pereriksson|Per Eriksson]] || || pereriksson || || Marketing Contact Sweden ||
|-
| Yaqiong Fang || X || fangyq || fangyq|| Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Hubert Figuière|| X || hub || hub || PPTX || Novell, Inc.
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || X || ufi || ufiooo || Application Help || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| [[User:Nf|Nils Fuhrmann]]|| || nf||SunNF||||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Peng Gao || || Gao Peng|| Gao Peng || writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Zemin Gao || || gaozemin|| gaozm || Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sophie Gautier|| X || sgauti|| sophi ||PL FR native-lang project, CC ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| [[User:Sg|Steffen Grund]]|| X || sg|| || NetBeans Integration ||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool, gsicheck, buildbot||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| X || lh ||lutzh||PL [http://ux.openoffice.org User Experience]||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Chuang Jiang || || jiangc || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jingchuan Kang|| || kangjingchuan || jingchuan || Surrogates in Unicode || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| [[User:pj@openoffice.org|Peter Junge]]|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Etsushi Kato || X || ekato || || Mac OS X Port || Independent
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Tobias Krause|| X || tkr||||ucb||Sun Microsystems
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||tl13||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
| Wind Li|| X || windly||||Address books||
|-
|Jian Li || || lijian || lijian|| Writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuan Li || || liyuan || || PyUNO, Async dialogs || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Weike Liang || || liangweike || liangweike || Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl || cl ||Graphic Applications||Sun Microsystems
|-
| Mindy Liu|| || mindyliu||||||
|-
|Jianli Liu || || liujl|| liujianli || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:liutao | LiuTao]] || X || liutao || liutao || PyUNO, Async dialogs,slideshow,modularization in SW || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|YU Liu || X || ch2000liuy || LiuYU || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuhua Liu || || liuyuhua|| yuhua|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:Dl|Dieter Loeschky]]|| X || dl ||||PL: ODF Toolkit||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||PhilippL||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Michel Loiseleur|| || mloiseleur|| coren`|| Bugfixes ||Linagora
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
|Jingrong Luo || || Luo Jingrong|| Luo Jingrong|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Xugang Lv || || lvxg || lvxg || XML Writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, PL JA, FreeBSD guy||Independent
|-
|Yonggang Mao || X || maoyonggang|| maoyg|| Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yue Lv || || lvyue || lvyue || Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
|-|
| Shane M Mathews|| X || smmathews|| smmathews ||[[Impress:_OpenGL_rendered_transitions]]||student
|-
| Frank Mau|| X || fma||||tooling||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Graduate
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man||RedHat, Inc.
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Ismael Merzaq|| X || isma87||ismael_||Mac OSX native porting||Student
|-
| Michael Mi|| || mmi||||||
|-
| Björn Michaelsen|| X || b_michaelsen ||Sweetshark|| ||Sun Microsystems
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| X || mmp|| mprove|| [[User Experience]], http://ux.openoffice.org || Sun Microsystems
|-
| Takashi Nakamoto|| || bluedwarf|| || ||
|-
| Jan Navrátil || X || jnavrati || jnavrati || || RedHat, Inc.
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||[[UnoApiTest]]||Sun Microsystems
|-
| Frank Neumann|| X || fne||||MacPort||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Jan Nieuwenhuizen|| X || jcn||janneke||Layout code, hacker ||Novell, Inc.
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Maximilian Odendahl|| X || mod||mod||[[Notes2]]|| Student / SEPT-Solutions
|-
| Lars Oppermann|| X || lo||||||Sun Microsystems
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| [[User:Fpe|Frank Peters]]|| X || fpe||||CL Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Sebastien Plisson|| X || plipli||plipli||Developer on Aqua port||OO Aqua Port
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Jonathan Pryor|| || jpryor || jonp || || Novell, Inc.
|-
| Canghua Qu|| || quch || Canghua || AutoTest, Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr|| drr ||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| Stella Schulze|| X || sts||||Visual Design||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
|Lei shi || || shilei|| sl || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Zhoubo Shi || || shizhoubo || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||Novell, Inc.
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| [[User:Muthusuba|Muthu Subramanian]]|| X || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
| Claus Sørensen|| || cs||c26n,cHBs,chbs||Danish Localization and Project Management Tool(oopm)||ProFOSS
|-
|Quanfa Tang || || tqfa|| tangquanfa|| Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||BrOffice.org
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| [[User:mt|Malte Timmermann]]|| X || mt|| Malte || Accessibility, Security, Performance||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||mav||Framework||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||VBA Interop||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| [[User:Weiz |Zhao Wei ]] || || weiz || weiz || chart, AODL || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Gerd Weiss|| X || gm||||RE||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker||RedHat, Inc.
|-
|[[User:wuy|Yan Wu]] || X || wuy || ||Framework || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Stephan Wunderlich|| X || sw||||||
|-
|Dehua Xu || || xudehua || xudh || Release || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||Novell, Inc.
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
|Huajun Zhang || || zhanghuajun|| zhanghj|| SW ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:Zhangxiaofei|Xiaofei Zhang]]|| || Zhangxiaofei || zhangxiaofei/FelixZ || [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jianwei Zhao || || zhaojianwei || zhaojianwei || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sheng zhao|| X || jacky23 || ||OdfToolKit_odf4j || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Fong Lin || X || pflin || Fong || CJK Enhancement/ Filter || Novell, Inc.
|-
| [[User:jza|Alexandro Colorado]]|| X || jza || jza|| CL [[OOoES|ES]] ||
|-
| Sunil Amitkumar Janki || || sjanki || sjanki || GNU Linux mipsel porter ||
|-
| [[User:Rescue|Joey Stanford]] || || Rescue/k0fcc || Rinchen || CL [http://eo.openoffice.org/ Esperanto native-lang project] || [http://canonical.com Canonical] ||
|-
| Mingfei Jia || X || jiamingfei || || Lotus Smart Suite filter || IBM Corp.
|-
| Xing Li || X || lixxing || || Accessibility || IBM Corp.
|-
| Wei Guo SHI || X || shiwg || || Accessibility and Smart Suite filter || IBM Corp.
|-
| Takashi Ono || X || tono || || MinGW port || Independent
|-
|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]]||QA Calc / Automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||writer, qa/qatesttool||QA Writer / Automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||draw, impress, qa/qatesttool||QA Graphics / Automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jogi||qa/qatesttool, [[Calc]]||Automation / QA Calc||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, qa/qatesttool||QA Base / Automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten|||| wg||||draw, impress||||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[Commit Rights]]
* [[Contributing Patches]]
* [[User Experience Community]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]
[[Category:Alpha Centauri]]