From OpenOffice.org Wiki

>]]

>]]

The source code can be fetched in several ways, as described below.

Source Tarballs (for package maintainers)

The latest release version of the source code can be downloaded as tarballs from Download, see Source on the right.

The source is pretty big and has therefore been split into several files.

For a full build you need them all. For development, the core package is usually all you need.

Unpack the tarballs one at a time to a directory. They will create a new directory with the name of the milestone, such as OOO310_m11. This folder will from now on be the $SRC_ROOT, when you run ./configure it will create a shell-script that will set the environment variable to this path.

Avoid using winzip to extract the downloaded source archive. Observed problems include: CR-LF errors that can affect makefiles and cause compile errors Certain files unpacked into root folder, esp. likely when actual path is deeply nested (e.g. foo/bar/source/foo/java/org/x/y/z/w/LongFileName.hmm) which again causes mysterious compile errors. Use the tar from Cygwin instead: unzip for .gz tar xvzf OOo_3.x.x_src_core.tar.gz bzip2 for .bz2 tar xvjf OOo_3.1.0_src_core.tar.bz2

SCM-Access for the current development line (named DEV300) using Mercurial as SCM

Mercurial (hg) replaces Subversion end of October 2009. The mercurial master repository is already in place. You can clone the repository with

hg clone http://hg.services.openoffice.org/DEV300 <working_dir>

The OOo Mercurial repository is huge. Cloning the OOo repository as shown above my take some hours depending on the quality of your internet connection. We provide a nightly snapshot as Mercurial bundle which is currently about 800 MB in size. Utilizing this bundle is the fastest way to get an initial clone of the repository.

Download the bundle here: http://hg.services.openoffice.org/bundle/DEV300.hg

mkdir <working_dir>
cd <working_dir>
hg init
hg unbundle <path_to_bundle>/DEV300.hg
hg pull http://hg.services.openoffice.org/DEV300
hg update

Both methods will get you a repository and a working tree with the latest changes.

List all available milestones (a stable development version released by RelEng):

hg tags

Checking out a milestone

hg update -rDEV300_mXX

For more information on using Mercurial with OOo, see: Mercurial Category:Mercurial

SCM-Access for the 3.2 release code line (named OOO320) using Subversion as SCM

Checking out a milestone (a stable development version released by RelEng)

svn checkout svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX/

Replace XX with the highest currently available milestone.

The files will be placed in the current directory.

See:

http://svn.services.openoffice.org/ooo/tags/

for a list of available milestones.

For more information on using Subversion with OOo, see: Setting up Subversion Access Using Subversion and the new CWS Tooling

See also

For pre-3.1 releases, see Getting the source (older versions).

1. ↑

   It's not absolutely necessary to build own versions for these modules on Linux. If you intend to build on Linux without the system tarball: You will need to tell ./configure explicitly to use the system libraries for the software that is otherwise contained in this tarball. Otherwise the build will fail. System software is in active development. If it has changed significantly (and Mozilla sometimes does), the build may fail or OpenOffice.org may not work correctly. unowinreg.dll - Do not be fooled by the .dll extension. Without it, the build will fail on Linux and it is not included in the core package. Don't worry about downloading this now because the build process will tell you where to get it and where to stick it to proceed.