Difference between revisions of "Getting the source"
Pereriksson2 (Talk | contribs) (filenames almost version independent + table + minor fixes) |
|||
Line 24: | Line 24: | ||
|OOo_3.x.x_src_sdk.tar.bz2 | |OOo_3.x.x_src_sdk.tar.bz2 | ||
|OOo Software Development Kit (SDK) | |OOo Software Development Kit (SDK) | ||
− | |||
− | |||
− | |||
|- | |- | ||
|OOo_3.x.x_src_testautomation.tar.bz2 | |OOo_3.x.x_src_testautomation.tar.bz2 | ||
− | | | + | |aoutomataed test suit (optional) |
|} | |} | ||
Revision as of 08:14, 3 July 2009
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.
Unpack these tarballs 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. If you intend to build on Linux without the system tarball:
For a full build you need them all. For development, src_core is usually all you need (but see the caveats for src_system above). Download them to one directory and unpack them. Information how to checkout from CVS follows. Vanilla buildYou might be interested particularly in the Get the source code section in the build guide. It is written for Linux, but it is quite similar for all the platforms. export 'CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs' cvs login (CVS password: anoncvs) cvs co -r <milestone> OpenOffice3 The tool to browse project source code online has some additional hints. If you want just to test development releases, you can download already compiled builds from [1]. List of available Mac builds is in Mac OS X Development Builds. SVN: See also OOo and Subversion Checking out a CWS through CVSThis section is a draft! First, find the CWS name such as picom. Then, lookup the CWS name in EIS (e.g., picom). Notice "Milestone (current)" is m222 (in this example as of time of writing): that is the base milestone. Then, notice the affected modules listed under "Modules & Files." You will checkout the base milestone from CVS. The convention for base milestone is SRC680_m### (later DEV300_m###?). Then in each affected module (where a module is basically a directory), you will update the module with CVS. The convention for the revision tag for the CWS is cws_src680_####. Here is a script.
#!/bin/bash # configure these variables according to the particular CWS AFFECTED_MODULES="basebmp basegfx canvas comphelper cppcanvas \ desktop filter goodies offapi offuh psprint sal \ slideshow solenv testshl2 tools unotools vcl xpdf" BASE_MILESTONE_TAG=SRC680_m222 CWS_TAG=cws_src680_picom export CVSROOT=':pserver:anoncvs@anoncvs.services.openoffice.org:/cvs' echo 'Enter the password is anoncvs' cvs login cvs co -r $BASE_MILESTONE_TAG OpenOffice2 for d in $AFFECTED_MODULES do echo "updating module $d" pushd $d cvs up -dP -r $CWS_TAG popd done
If you have a working ~/.cwsrc configuration file setup and the SOLARENV environment variable is set to an already existing solenv directory of a previously checked out OOo tree, e.g. You also may use cwsquery to obtain the current milestone of the CWS with
When scripting this it is a good idea to check the exit code of cwsquery commands in case your ~/.cwsrc is broken or the environment prerequisites aren't met or the EIS database isn't reachable, so add the following after each cwsquery command:
if [ $? -ne 0 ]; then echo 'cwsquery unsuccessful.' exit 1 fi
If you already have ~/.cwsrc working and a milestone master build ready and want to work on a CWS based on that milestone see Tuning in to a CWS, which offers a method that does not require to rebuild the entire tree. External links
See also |
|