Difference between revisions of "Building ooo-build on Mac OS X"
From Apache OpenOffice Wiki
| Line 6: | Line 6: | ||
After installing (mind the order, MacPorts need XCode, and making sure that your firewall permits traffic on port 873 (rsync), needed for MacPorts' selfupdate): | After installing (mind the order, MacPorts need XCode, and making sure that your firewall permits traffic on port 873 (rsync), needed for MacPorts' selfupdate): | ||
| − | * make sure your shell path contains /opt/local/bin (open new shell or reboot) | + | * make sure your shell path contains /opt/local/bin (open new shell or reboot, if that fails) |
| + | echo "export PATH=/opt/local/bin:${PATH}" >> ~/.profile | ||
* install the following extra packages via | * install the following extra packages via | ||
| − | sudo port install autoconf automake subversion pkgconfig wget coreutils | + | sudo port install autoconf automake subversion pkgconfig wget coreutils p5-archive-zip |
| − | + | ||
| − | + | ||
| − | + | ||
My current configure line is: | My current configure line is: | ||
Revision as of 16:43, 11 September 2008
It's actually pretty simple, apart from grabbing the ooo-build tree as explained on Building with ooobuild, you need:
- for Leopard (10.5) XCode 3.0 or better (free ADC download)
- for Tiger (10.4) XCode 2.4.1 or better (free ADC download)
- MacPorts (from here) - the dmg installer version is prolly easiest & safe
After installing (mind the order, MacPorts need XCode, and making sure that your firewall permits traffic on port 873 (rsync), needed for MacPorts' selfupdate):
- make sure your shell path contains /opt/local/bin (open new shell or reboot, if that fails)
echo "export PATH=/opt/local/bin:${PATH}" >> ~/.profile
- install the following extra packages via
sudo port install autoconf automake subversion pkgconfig wget coreutils p5-archive-zip
My current configure line is:
./autogen.sh --with-distro=MacOSX --disable-mozilla --disable-build-mozilla --disable-report-builder --disable-gtk
followed by
./download && make
and
bin/ooinstall -l <path_to_your_dev_installation>
should get you a freshly built OOo at <path_to_your_dev_installation>, already with libraries (mostly) symlinked to the source trees.
