Prerequisites for Mac OS X/Homebrew - Revision history

Popcorndude: add link to updated instructions

2019-05-12T19:36:32Z

add link to updated instructions

Rcrowther at 15:20, 26 September 2016

2016-09-26T15:20:25Z

Unhammer at 14:14, 15 January 2016

2016-01-15T14:14:40Z

Unhammer at 14:13, 15 January 2016

2016-01-15T14:13:22Z

Unhammer at 14:12, 15 January 2016

2016-01-15T14:12:58Z

Unhammer: Created page with "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..."

2016-01-15T14:11:46Z

Created page with "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..."

New page

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.

[https://github.com/unhammer/apertium-get/blob/master/.travis.yml This script] for testing on https://travis-ci.org uses <code>brew install gperftools help2man pcre icu4c perl518 gawk</code>, but travis comes with some stuff preinstalled, so you may also need to <code>brew install autoconf automake pkg-config subversion cmake wget apple-gcc42</code>.

Note also the <code>CMAKE_PREFIX_PATH=/usr/local/opt/icu4c:"${CMAKE_PREFIX_PATH}" ./cmake.sh</code> – 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.

[[Category:Installation]]

← Older revision		Revision as of 19:36, 12 May 2019
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.

← Older revision		Revision as of 15:20, 26 September 2016
Line 17:		Line 17:

	[[Category:Installation]]		[[Category:Installation]]
			[[Category:Documentation in English]]

@@ Line 9: / Line 9: @@
 That said, you should probably stick with Macports if you can.
-==See also==
+==External links==
-* http://brew.sh/
+* http://brew.sh/ – Homebrew homepage

@@ Line 9: / Line 9: @@
 That said, you should probably stick with Macports if you can.
+==See also==
+* http://brew.sh/

@@ Line 1: / Line 1: @@
 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.
+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 [http://brew.sh homebrew] itself.
 [https://github.com/unhammer/apertium-get/blob/master/.travis.yml This script] for testing on https://travis-ci.org uses <code>brew install gperftools help2man pcre icu4c perl518 gawk</code>, but travis comes with some stuff preinstalled, so you may also need to <code>brew install autoconf automake pkg-config subversion cmake wget apple-gcc42</code>.
 Note also the <code>CMAKE_PREFIX_PATH=/usr/local/opt/icu4c:"${CMAKE_PREFIX_PATH}" ./cmake.sh</code> – 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.