Building GCCSDK on Mac OS X: Difference between revisions
(Create basic installation guide (work in progress)) |
No edit summary |
||
| Line 1: | Line 1: | ||
= Building GCCSDK on Mac OS X = |
|||
Mac OS X provides a Unix-style environment, so building GCCSDK is broadly similar to the [[Using GCCSDK|Linux instructions]] which you should also read. However the packages to be installed are different. This guide is based on Mac OS X 10.9 Mavericks - other systems may vary. |
Mac OS X provides a Unix-style environment, so building GCCSDK is broadly similar to the [[Using GCCSDK|Linux instructions]] which you should also read. However the packages to be installed are different. This guide is based on Mac OS X 10.9 Mavericks - other systems may vary. |
||
| Line 16: | Line 14: | ||
intltool<br/> |
intltool<br/> |
||
help2man<br/> |
help2man<br/> |
||
| ⚫ | |||
gperftools<br/> |
gperftools<br/> |
||
| ⚫ | |||
mpfr2<br/> |
|||
orbit<br/> |
orbit<br/> |
||
pkg-config<br/> |
pkg-config<br/> |
||
Latest revision as of 18:40, 8 December 2013
Mac OS X provides a Unix-style environment, so building GCCSDK is broadly similar to the Linux instructions which you should also read. However the packages to be installed are different. This guide is based on Mac OS X 10.9 Mavericks - other systems may vary.
First you will need Apple's command line environment. Type 'strings' in a terminal and, if you're missing the 'strings' program, it should offer to install the tools.
This guide uses packages from the Homebrew project. Install Homebrew by following the instructions. Packages can then be installed using 'brew install packagename'. These packages are required for GCCSDK:
autoconf213
autogen
automake
coreutils
cvs
doxygen
dpkg
intltool
help2man
gperftools
mpc
mpfr2
orbit
pkg-config
svn
wget
To build, do:
export PATH="$(brew --prefix coreutils)/libexec/gnubin:$PATH" ./build-world
in your terminal. The first line ensures GNU tools like 'cp' and 'readline' take precedence over the internal Mac OS tools (which are based on FreeBSD).
