Getting the source
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.
|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 system1. 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.
SCM-Access (for developers)
Checking out a milestone (a stable development version released by RelEng
Replace XX with the highest currently available milestone.
The files will be placed in the current directory.
|Content on this page is licensed under the Public Documentation License (PDL).|