Difference between revisions of "Documentation/Building Guide/Getting the source"
B michaelsen (Talk | contribs) m (→Source Tarballs (for package maintainers)) |
B michaelsen (Talk | contribs) m |
||
| Line 70: | Line 70: | ||
for a list of available milestones. | for a list of available milestones. | ||
| − | + | {{Template:Documentation/Note|For more information on using Subversion with OOo, see: | |
* [[Setting up Subversion Access]] | * [[Setting up Subversion Access]] | ||
| − | + | * [[OOo and Subversion|Using Subversion and the new CWS Tooling]]}} | |
| − | * [[OOo and Subversion|Using Subversion and the new CWS Tooling]] | + | {{Template:Documentation/Tip|Mercurial will soon replace Subversion. For more information on using Mercurial with OOo, see: |
| − | + | * [[Mercurial Pilot]] | |
| − | * [[Mercurial Pilot]] | + | * [[OOo and Mercurial]]}} |
| − | + | ||
| − | * [[OOo and Mercurial]] | + | |
= See also = | = See also = | ||
| − | + | {{Template:Documentation/Note|For pre-3.1 releases, see [[Getting the source (older versions)]].}} | |
| − | + | ||
= Footnotes = | = Footnotes = | ||
Revision as of 11:09, 17 July 2009
| Building Guide
|
| Introduction Getting the source |
The source code can be fetched in several ways, as described below.
Contents
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 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
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. Template:Documentation/Note Template:Documentation/Tip
See also
Footnotes
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.
| Content on this page is licensed under the Public Documentation License (PDL). |
