NeoOffice Build Instructions

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 06:39, 29 November 2005 (edit)
Sardisson (Talk | contribs)
(→CVS tags - more about the current stable branch)
← Previous diff		 Current revision (15:51, 20 August 2016) (edit) (undo)
( | contribs)
(Remove extraneous language bar)
 
(58 intermediate revisions not shown.)
Line 1: Line 1:
-== Building and Developing NeoOffice ==+{{redbox|'''Important:''' If you redistribute your personal builds, you '''must''' remove all instances of the NeoOffice trademark (including those present within graphics) in order to be in compliance with the [[NeoOffice_CD_Distribution_%26_Trademark_Usage|NeoOffice Distribution & Trademark Usage Policy]]. '''Distribution of non-official builds using the NeoOffice trademark is prohibited.'''}}
-===Build Instructions===+NeoOffice build instructions are [http://www.neooffice.org/neojava/build.php here].
- +
-Patrick Luby maintains the NeoOffice build instructions at +
-http://www.planamesa.com/neojava/build.php+
- +
-Because building NeoOffice requires building [[OpenOffice.org_Mac_OS_X_%28X11%29|OpenOffice.org/X11]], you might find the [http://porting.openoffice.org/mac/build_11_X11.html OpenOffice.org 1.1.x for Mac OS X build instructions] helpful (if you are trying to build HEAD—which may not build at present—the [http://porting.openoffice.org/mac/build_680_X11.html OpenOffice.org 2.0.x for Mac OS X build instructions] might be helpful).+
- +
-===Getting Help===+
- +
-[http://porting.openoffice.org/servlets/SummarizeList?listName=dev Archives] of the [mailto:dev@porting.openoffice.org dev@porting.openoffice.org] mailing list are useful; you can search them for errors you encounter.+
- +
-You can also post questions in the [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=9 NeoOffice Development] forum on trinity (and search it for errors), but be aware that the NeoOffice developers consider the process of compiling OpenOffice.org (even as a subset of NeoOffice) as a [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=8775#8775 "trial by fire"] and little hand-holding is available. +
- +
-Experience has shown that those who are unable to work through the OpenOffice.org build will be unable to do the debugging and other work necessary when adding code or fixing an existing bug in OpenOffice.org or NeoOffice. (Such "hand-holding" also cuts into the limited time the volunteer developers have to fix actual bugs and improve Mac OS X integration.)+
- +
-Building OpenOffice.org on the Mac (and by extension NeoOffice) is often difficult because there is always some change to the code for Linux or Windows that makes OOo no longer buildable on Mac OS X. Sun's engineers do not build on Mac OS X so changes for Windows or Linux can easily break the build on Mac OS X and undetected. Also, Sun routinely does not merge Mac OS X fixes into the next build. A patch may be integrated in the OOo 1.1.3 code but then not merged into the OOo 1.1.4 code, and fixes from the OOo 1.1.x codeline will not appear in the OOo 2.x codeline.+
- +
-===Source Code===+
- +
-NeoOffice source code is available as a tarball on the latest release or milestone disk image; the latest code is always available in [http://www.planamesa.com/neojava/build.php cvs].+
- +
-You can also [http://trinity.neooffice.org/cgi-bin/cvsweb/neojava/ browse the NeoOffice source online].+
- +
-====CVS tags====+
-''for use in the cvs checkout commands in the [http://www.planamesa.com/neojava/build.php NeoOffice Build Instructions]; in the format <tt>tag modulename</tt>'' +
- +
-A "release" tag checks out the code of a full release or milestone version (e.g., NeoOffice 1.2 Alpha) as available on planamesa.com but '''does not include any subsequent patches or bugfixes'''. A "stable branch" tag will check out the latest code for an active branch, including any code delivered in any released patches and any code recently committed to fix bugs (a "stable branch" that is current may have future milestones or releases based on it, e.g. the 1.2 Branch will be the basis of NeoOffice 1.2 Beta and NeoOffice 1.2 "final" at some point). A "development" tag is the site of ongoing future development and '''may not even build''' yet. You can find additional "legacy" tags by [http://trinity.neooffice.org/cgi-bin/cvsweb/neojava/ browsing cvsweb].+
- +
-<u>Current</u>+
- +
-'''Release''' (''NeoOffice 1.2 Alpha''): <tt>NeoOffice-1_2_Alpha NeoOffice</tt>+
- +
-'''Stable Branch''' (''1.2 Branch''): <tt>NeoOffice-1_2_branch NeoOffice</tt>+
- +
-'''Development''' (''attempts to build using OpenOffice_2_0_0 branch''): <tt>HEAD NeoOffice</tt>+
- +
-<u>Legacy</u>+
- +
-'''Release''' (''NeoOffice/J 1.1''): <tt>NeoOfficeJ-1_1 NeoOfficeJ</tt>+
- +
-'''Stable Branch''' (''1.1 Branch''): <tt>NeoOfficeJ-1_1_branch NeoOfficeJ</tt>+
- +
-'''Development''' (''MacIntel effort for 1.1 series''): <tt>gcc4_x86_experimental_branch NeoOfficeJ</tt>+
- +
-===Forum Threads===+
-''The following threads or posts from trinity '''may''' contain useful tips for beginners wishing to build NeoOffice:''+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=11298#11298 Setting up your build environment]+
-: Along those lines, the NeoOffice developers also build the OpenOffice.org dependencies themselves rather than relying on Fink or DarwinPorts.+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1364 Errors on Build]+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1508 Tips for Building Neo/J]+
-: '''N.B.''' the above threads apply to the NeoOffice/J 1.1 release; the build requirements have changed slightly beginning with NeoOffice 1.2 Alpha.+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1498 Compiling HEAD on 10.4]+
-: These changes have all been committed to HEAD and the NeoOffice 1.2 Alpha codebase, but there are some helpful tips about the NeoOffice build system and cvs in the later pages of the thread.+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=11465#11465 More explanation of the Neo build system]+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1733 gcc4 porting]+
-: For those crazy enough to live on the bleeding edge, or those with Developer Transition Kits :-)+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=11238#11238 More cvs tips]+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=2013 CVS tags for NeoOffice 1.2 release, NeoOffice 1.2 branch, and future MacIntel porting work]+
-* [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=13934#13934 Xcode versions for HEAD/NeoOffice 2.0]+
- +
-===Development Plans===+
- +
-For reference, the current (late 2005-2006) development plans are roughly outlined in [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1481 this thread].+
- +
-You can also check [http://bugzilla.neooffice.org/query.php?op=doquery&status%5b%5d=2 the bugs marked New/Deferred] in Bugzilla to see specific items the developers plan on implementing as time and resources permit.+
- +
-Ed Peterlin also maintains [http://www.dashboardbuddha.com/OOo/specs/index.html a set of specifications] for adding Mac-specific features (or, things he'd like to add, if he ever gets time after adding Aqua widgets!).+
- +
-[[Category:NeoOffice/J]][[Category:Contributing]]+

Current revision

Important: If you redistribute your personal builds, you must remove all instances of the NeoOffice trademark (including those present within graphics) in order to be in compliance with the NeoOffice Distribution & Trademark Usage Policy. Distribution of non-official builds using the NeoOffice trademark is prohibited.

NeoOffice build instructions are here.

Retrieved from "https://neowiki.neooffice.org/index.php/NeoOffice_Build_Instructions"
Personal tools