Difference between revisions of "Prerequisites for Mac OS X/Homebrew"

From Apertium
Jump to navigation Jump to search
m
(add link to updated instructions)
 
Line 1: Line 1:
  +
<div style="background-color:pink; text-align:center; line-height:2.5; border: 1px solid crimson;">Are you sure this is the page you want?<br/>If not, you probably actually want [[Apertium_on_Mac_OS_X]]<br/>If you're here because the instructions on that page didn't work for you, log on to [[IRC]] and describe what went wrong.</div>
  +
 
This page shows how to use '''brew''' to install the standard dependencies of apertium (and related packages) on Mac OS X.
 
This page shows how to use '''brew''' to install the standard dependencies of apertium (and related packages) on Mac OS X.
   

Latest revision as of 19:36, 12 May 2019

Are you sure this is the page you want?
If not, you probably actually want Apertium_on_Mac_OS_X
If you're here because the instructions on that page didn't work for you, log on to IRC and describe what went wrong.

This page shows how to use brew to install the standard dependencies of apertium (and related packages) on Mac OS X.


Most of our OS X developers use port, not brew, but it should be perfectly possible to install prerequisites using brew. As with Macports, you need the full XCode with command-line-tools, and of course homebrew itself.

This script for testing on https://travis-ci.org uses brew install gperftools help2man pcre icu4c perl518 gawk, but travis comes with some stuff preinstalled, so you may also need to brew install autoconf automake pkg-config subversion cmake wget apple-gcc42.


Note also the CMAKE_PREFIX_PATH=/usr/local/opt/icu4c:"${CMAKE_PREFIX_PATH}" ./cmake.sh – if "brew" tells you that something was kegged and you need to set LDADD/CPPFLAGS, then you can put it in CMAKE_PREFIX_PATH when running ./cmake.sh.


That said, you should probably stick with Macports if you can.

External links[edit]