![]() Note: You can alternatively use the libart_lgpl library instead of GPC. In this case simply follow the instructions given here on this website to solve the problem.Īttention: Direct Link to the download but it's only a few hundred KB. Note: In some cases using CPAN with Mac OS X is a bit problematic. If you're not 100% sure what to answer simply accept the default answers. If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. To install Archive::Zip use the following commands in Terminal.app: Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree. To get a second copy of the sources use the following commands within your 680_mXXX directory:Īdditional software that's not in the official sources The protocol runs on port 2401, and some firewalls will not allow communication on this port.Īttention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.įor further information on this topic see get the source Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. go get some coffee, or a beer, since it'll take a while to get it all Open a new Terminal (/Applications/Utilities/Terminal)įor later milestones simply replace the XXX with the most current milestonenumberĨ. If you've built from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.ĭownload the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):ġ. Once you have X properly installed, it's time to get the sources and other external sources. Getting and External Sources Getting Source from CVS bin/tcsh or -tcsh means you are using the c-shell bin/bash or -bash means you are using bash The output shows you which shell you're currently using. To determine the shell you currently use open Terminal.app and type the following command: Where necessary this read-me distinguishes between bash and tcsh. If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x. The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash. One and that's probably not what you want.ĭetermine the shell you use for compilation In the meantime cvs sources could have been edited and you need to recompile more modules then just With a second set of clean sources you can easily go back to clean sources if a module doesn't build,Ī patch doesn't solve the problem, you have to revert a patch or for any other reason there may be. * If you can afford it we recommend you to backup clean sources and work with a second set of sources. More localizations means more disk space needed.Ī minimum of 18GB for a full debug build. Note: Usage of disk space depends upon the number of localizations you build for. * A minimum of 4 to 5GB for a standard build. * You need a version of in your path for some modules We recommend Apple's X11 but you can also use the ones of X.org or Xfree86 * JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers) Note: You can get both applications after a free registration at * on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for * Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for Requirements * The fastest machine you can find. The coders and supporters behind the Mac port are: To get this information we recommend you to subscribe to our porting mailing list you'll get all the latest information about patches and everything else related to and needed to port to the Mac.īefore we begin let me thank all the people without whom these build instructions would make no sense, the coders who are helping to bring OOo 2.0 to Mac OS X. These build instructions are based upon milestone 680_m140 and higher.ĭue to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. 9 Building the whole suite or just a single Project with Debug Informationīuilding X11 for Mac OS X PPC and Mac OS X x86.8.1 Additional Information for Macports Users.7.2 Adding unowinreg.dll to OOo sources.6.2 Additional software that's not in the official sources. ![]() 5 Determine the shell you use for compilation.1 Building X11 for Mac OS X PPC and Mac OS X x86.
0 Comments
Leave a Reply. |