Difference between revisions of "Getting the source"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) m (→Checking out from Subversion) |
B michaelsen (Talk | contribs) (footnoted auxilary info, added toc) |
||
| Line 1: | Line 1: | ||
{| | {| | ||
| − | | | + | |- |
| − | + | | __TOC__ | |
| + | |{{Getting_It|Languages}} | ||
| + | |} | ||
The source code can be fetched in several ways, as described below. | The source code can be fetched in several ways, as described below. | ||
| − | + | = Source Tarballs (for package maintainers) = | |
The latest version of the source code can be downloaded as tarballs from [http://download.openoffice.org/ Download], see '''Source''' on the right. | The latest version of the source code can be downloaded as tarballs from [http://download.openoffice.org/ Download], see '''Source''' on the right. | ||
| Line 20: | Line 22: | ||
|- | |- | ||
|OOo_3.x.x_src_system.tar.bz2 | |OOo_3.x.x_src_system.tar.bz2 | ||
| − | |Libraries that usually exist on a standard Linux system. It's not absolutely necessary to build own version on Linux. For a Windows build this package is usually required. | + | |Libraries that usually exist on a standard Linux system. It's not absolutely necessary to build own version on Linux.<sup>[[#Foot1|1]]</sup> For a Windows build this package is usually required. |
|- | |- | ||
|OOo_3.x.x_src_binfilter.tar.bz2 | |OOo_3.x.x_src_binfilter.tar.bz2 | ||
| Line 39: | Line 41: | ||
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''', so set this environment variable to this path on your machine. | 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''', so set this environment variable to this path on your machine. | ||
| − | + | = SCM-Access (for developers) = | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Checking out the source code from the Subversion tree can be done in the following ways. | Checking out the source code from the Subversion tree can be done in the following ways. | ||
| Line 54: | Line 51: | ||
The files will be placed in the current directory. | The files will be placed in the current directory. | ||
| − | + | == More information on SCM == | |
| − | [http://tools.openoffice.org/svn_checkout.html Acessing the source code repository] | + | [http://tools.openoffice.org/svn_checkout.html Acessing the source code repository] |
| + | |||
[[OOo and Subversion]] | [[OOo and Subversion]] | ||
| − | + | [[Setting_up_Subversion_Access]] | |
| − | + | = See also = | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | * [[Building]] | ||
| + | * [[Getting it 2.4.x]] | ||
| + | = Footnotes = | ||
| + | <span id="Foot1"><sup>1</sup> If you intend to build on Linux <strong>without</strong> 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. | ||
| + | </span> | ||
[[Category:Development]][[Category:Build_System]] | [[Category:Development]][[Category:Build_System]] | ||
Revision as of 16:02, 16 July 2009
|
The source code can be fetched in several ways, as described below.
Source Tarballs (for package maintainers)
The latest 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. It's not absolutely necessary to build own version on Linux.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 | OOo 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, so set this environment variable to this path on your machine.
SCM-Access (for developers)
Checking out the source code from the Subversion tree can be done in the following ways.
Checking out the trunk (main development branch)
svn checkout svn://svn.services.openoffice.org/ooo/trunk
The files will be placed in the current directory.
More information on SCM
Acessing the source code repository
See also
Footnotes
1 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.
