Getting the source

From Wiki
Revision as of 09:14, 6 September 2011 by Sancho (talk | contribs)
Jump to navigationJump to search
[[{{{PrevPage}}}|<

Previous Page ]]

[[{{{NextPage}}}|

Next Page

>]]


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


SCM access for the current development line (named DEV300) using Mercurial

Mercurial (hg) replaced Subversion in October 2009. You can clone the master 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 1.3 GB 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
Tip.png For more information on using Mercurial with OOo, see:

SCM access for the 3.3 release code line (named OOO330) using Mercurial

The OOo Mercurial repository is huge. We provide a nightly snapshot as Mercurial bundle which is currently about 1.4 GB in size. Using this bundle is the fastest way to get an initial clone of the repository.

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

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

Checking out a milestone

hg update -r OOO330_mXX

You can clone the repository as well, but it will take much longer than the bundle

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


SCM access for the 3.2 release code line (named OOO320) using Mercurial

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

Just look at the instructions for 3.3 above, and replace OOO330 with OOO320.


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.

Tarball Description
OOo_3.x.x_src_core.tar.bz2 The necessary part for each build, the other tarballs depend on this one.
OOo_3.x.x_src_system.tar.bz2 Libraries that usually exist on a standard Linux system[1]. For a Windows build this package is usually required.
OOo_3.x.x_src_binfilter.tar.bz2 The filters for old binary StarOffice formats
OOo_3.x.x_src_l10n.tar.bz2 Translations of the software for many languages
OOo_3.x.x_src_extensions.tar.bz2 Extensions source package
OOo_3.x.x_src_testautomation.tar.bz2 Automated test suite (optional)

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.

Documentation caution.png 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.x.x_src_core.tar.bz2


See also

Documentation note.png For pre-3.2 releases, see Getting the source (older versions).

  1. Documentation note.png 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.
Content on this page is licensed under the Public Documentation License (PDL).