Difference between revisions of "Documentation/Building Guide/Building on MacOSX/checkout for milestones before m32"
B michaelsen (Talk | contribs) m |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Old|EN}} | |
| + | {{Note|Get the source from CVS (only for old milestones i.e. before DEV300m32)}} | ||
For previous milestones (means before m31) : cvs is mandatory | For previous milestones (means before m31) : cvs is mandatory | ||
Latest revision as of 12:52, 9 July 2018
This article is outdated.  |
Get the source from CVS (only for old milestones i.e. before DEV300m32) |
For previous milestones (means before m31) : cvs is mandatory
=> Prepare a directory for the source download
mkdir DEV300_m30 cd DEV300_m30
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs" cvs login (password is 'anoncvs' ) + Enter
cvs -z3 co -r DEV300_m30 OpenOffice3 swext apache-commons tomcat hyphen hunspell cppunit # don't forget the "3" !!
Note: swext, tomcat, etc. in the cvs checkout are needed to prevent breakages at buildtime
IMPORTANT : if you want to build an old version of OpenOffice.org on Mac OS X (especially for SRC680 versions) ,
you MUST use these mozilla archives instead :
http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBinc.zip
http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBlib.zip
http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBruntime.zip
If you want to build using them on PowerPC or Intel architecture (with Tiger) please rename them this way :
| Archive | Name in Intel architecture | Name on PowerPC architecture |
| headers | MACOSXGCCIinc.zip | MACOSXGCCPinc.zip |
| runtime | MACOSXGCCIruntime.zip | MACOSXGCCPlib.zip |
| libs | MACOSXGCCIlib.zip | MACOSXGCCPlib.zip |
As you can see, P means PowerPC, and I means Intel (replacing U or the UB (it depends on the builder) in the original name)
.. and put them into <ooo build directory>/DEV300_m28/moz/zipped Once done, you'll obtain milestone m28 from DEV300.
OpenOffice.org should detect and use them if you respect the configure command line as described in Milestone build.
