| [[{{{PrevPage}}} < Previous Page ]] | [[{{{NextPage}}} Next Page |
Dec 13, 2015 Installing Apache OpenOffice On MAC Mac OS (Operating System),OpenOffice (Software),Apache Software Foundation (Membership Organization),How-to (Website Category),Macintosh (Video Game Platform. How to Easily Uninstall Apache OpenOffice for Mac. Bernice Curry; 17-12-08 9:09; 5384; Decide to uninstall Apache OpenOffice on your Mac? Wish to have a clean and complete uninstall rather than simply drag OpenOffice to the Trash? If you have any doubt about removing OpenOffice, check out this post to get the correct answers. Apache OpenOffice for Mac is the leading open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more.It is available in many languages and works on all common computers.
How do I install OpenOffice on Mac OS X? Visit the OpenOffice website at and locate the icon with the download option on the top menu bar of the website with the word 'Download'. Click on it and you will be presented with a green area holding some options. Apache OpenOffice for Mac is the leading open-source office software suite for word processing, spreadsheets, presentations, graphics, databases and more.It is available in many languages and works on all common computers. It stores all your data in an international open standard format and can also read and write files from other common office software packages. Apache OpenOffice for Mac Download Apache OpenOffice is an open-source office productivity software suite It is one of the successor projects of OpenOffice.org and integrates features and improvements from IBM Lotus Symphony Apache.
This document explains how to build older OpenOffice source code on Mac OS X systems.
$SRC_ROOT will denote the directory in which the source code of Apache OpenOffice is stored. |
| You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases. |
To build the office on Mac OS X several requirements/prerequisites have to be fulfilled.
This library is Windows only but will be packed in the Apache OpenOffice SDK to ensure that it is available on all platforms. The library provides some glue code to setup a working UNO environment for UNO client applications connecting to an office and doing some remote automation via API. The library should be stored in main/external/unowinreg. Only necessary for building the SDK.
The library can be downloaded under
If you intend to build Apache OpenOffice several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.
You can install it using Fink. It is simply named 'ccache'. For MacPorts users the package is called 'ccache'.
If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/
There are two ways to enable ccache - one is to set environment variables, the other way is to use symlinks.
Using environment variables:
Using the symlink approach:
for both methody, you can add the 'export ..' lines to your ~/.profile - that way you don't need to manually set it when building. You can still temporarily disable ccache (export CCACHE_DISABLE=1) in case you don't want to use it.
Since OOo is rather huge, you should increase the cache-size to 1 GB or more
Since OOo's source code is managed using Subversion currently, you also need the svn client to checkout sources (otherwise you would be bount to source-tarballs that aren't generated that frequently). You can either compile yourself or use the subversion universal binaries from the subversion project Version 1.5.4 or later is required because of important fixes related to the merge-feature.
You need about 4.7 GB for a checkout from the svn repository. Building the source requires another 5GB.
Apache OpenOffice build environment is configured using the open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, is now done in the main source directory.
To save the configure parameters and use them with different milestones it is useful to create your own build script to configure the environment and to trigger the build.
The directory structure when you have checked out the sources from svn looks like:
Move into main and configure a minimal environment to build your first version of Apache OpenOffice:
Run the autoconf command to prepare a new configure based on the latest changes in configure.in
Run configure
This commands prepares a minimal environment to build the office without any category-b enabled external libraries. A pure Apache license compatible version. See also the configure switches --with-dmake-path and --with-epm to specify prebuilt versions of dmake or epm.
Finally you should run bootstrap to trigger further preparations and to create platform specific shell script to setup a working build environment. On Mac OS x for example MacOSXX86Env.Set.sh on a Intel based system.
To prepare a build environment that provides more features and make use of further external libraries which are under copyleft but viral licenses you have to explicitly enable this category-b components.
As mentioned before to save the configure parameters and use them with different versions it is useful to create your own build script to configure the environment.
Create 'build.sh' (to be written) :
Put this script into ~/bin and make sure it is executable :
We used the bash shell in all example, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description OpenOffice.org's Build Environment.
After running configure and bootstrap we should have a working build environment and all necessary scripts should have been created. From now on you can use MacOSXX86Env.Set.sh to prepare a new shell with a working build environment.
TODO TODO TODO ..
if you run into trouble with --dlv_switch (see: Issue 77360 )
The main purpose of the bootstrap script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html
Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for running svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see Environment_Variables. Please note that on Intel machines, 'MacOSXPPCEnv.Set.sh' should be substituted with 'MacOSXX86Env.Set.sh'.
This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTEL iMac). Be patient.
If you want to see how the progress on that build is you can use two build options to get a comfortable view:
where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file unxmacxi.pro.build.html via the in Mac OS X included Apache web server or diretctly form the directory /Users/$USER/Sites/. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.
Quicken business for mac. If you are redeeming the free Quicken Starter product through the purchase of TurboTax, and you are currently in an active Quicken subscription and not within 6 months of your renewal date, you will have to return to this page within 6 months of renewal in order to redeem.
If you build on Snow Leopard (aka Mac OS X 10.6): Set DYLD_INSERT_LIBRARIES to point to the correct libsqlite3.dylib:
Once the build completed, the final product ( en-US version ) is named : OOo_3.0.0_*_MacOSXIntel_install.dmg ( for version 3.0beta e.g.)
And is located in instsetoo_native/unxmacxi.pro/OpenOffice/dmg/install/en-US directory ( replace en-US with your locale )
Now you can start to work with this amazing productivity suite.
Application switches are often valuable for isolating a problem. Most of OpenOffice.org's options can be found its Tools->Options menu.
Some switches are so special that there is no user interface to change them. They are only useful for debugging and isolating a problem, but they are very valuable a that. So a developer might suggest to isolate a problem by setting an environment variable before running the application. E.g. for isolating problems with the menubar a developer might suggest to set the environment variable AQUA_NATIVE_MENUS to false. This is done by typing these commands into a terminal:
Please note that bugs involving crashes should provide a description of how to reproduce the problem and a callstack.There are several ways to provide the callstack:
Check the list of open issues
Report new issues after you have isolated the problem
Debugging problems is often easier in an development environment:
Please note that XCode still has some problems with the executable named soffice.bin (because of the dot in the name). The issue has been reported to xcode-users list.
With OOO300 the Aqua port became a mainstream port, so most Aqua issues are handled in regular GSL-Layer childworkspaces instead of dedicated Aqua CWSses. Other CWSses that are purely Aqua specific are being tracked below:
All patches that developers have that need testing or peer review should be added here.
A historical overview of old Aqua specific ChildWorkspaces.