Joined: Apr 25, 2006 Posts: 2315 Location: Montpellier, France
Posted: Sun Oct 29, 2006 4:20 pm Post subject:
Since patches can contain files from several modules, and may need some OpenOffice.org code to build, the source code for each patch can't just be bundled with the patch itself, and a patch can't be built separately from NeoOffice (i.e. it requires an existing build, and builds on top of that).
In order to build a patch, you need to build NeoOffice with the latest code from the HEAD branch.
Moreover, since code built with another version of Xcode can't be mixed with that of the official builds (doing so would render Neooffice unusable - meaning that it wouldn't launch), official patches won't install on custom builds, an vice-versa (the patch installer will check, and then claim that NeoOffice isn't installed on your hard drive). So to keep your personal build up-to-date, you'll have to switch your workspace to HEAD, and rebuild NeoOffice as the code gets updated (fortunately, you won't have to do a full rebuild, just rebuild the updated modules).
Joined: Jun 16, 2003 Posts: 11847 Location: California, USA
Posted: Sun Oct 29, 2006 4:22 pm Post subject:
Moving to NeoOffice Development forum.
To get the patch source, you just check out the latest NeoOffice code instead of the "NeoOffice-2_0_Aqua_Beta_3" CVS tag. To update to the lastest code in your existing build you need to do the following steps:
1. "rm -Rf" the following directories in your neojava directory: desktop, fpicker, jvmfwk, sal, sc, sfx2, shell, svtools, and vcl.
2. "cvs update -Ad" your neojava directory. The "-A" forces you to get the latest code in the NeoOffice CVS tree.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum