Difference between revisions of "Development:Building:Building Dependencies from Source"
(→Building the Packages: flip this around now that we are using the suffix) |
m (and one last 2.13) |
||
| Line 1: | Line 1: | ||
| − | Some people prefer to build their dependencies ( | + | Some people prefer to build their dependencies (<code>libIDL-0.8</code>, <code>autoconf-2.13</code>) from source instead of using [http://www.finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] and the megabytes of extra software those port systems install by default. Fortunately, it is rather trivial to build the required dependencies from source. |
==Dependency Tree== | ==Dependency Tree== | ||
Revision as of 22:52, 18 May 2009
Some people prefer to build their dependencies (libIDL-0.8, autoconf-2.13) from source instead of using Fink or MacPorts and the megabytes of extra software those port systems install by default. Fortunately, it is rather trivial to build the required dependencies from source.
Contents
Dependency Tree
Building the Packages
You can install all these packages in /usr/local (where they should be picked up by your $PATH automatically). You should be very careful when building autoconf-2.13 so that you do not create an autoconf binary that will be used accidentally when scripts want the version of autoconf installed with Xcode; make sure you use the --program-suffix=213 argument.
autoconf-2.13
autoconf-2.13 has no dependencies aside from software installed with Xcode.
- Download the
autoconf-2.13tarball and unpack. cdto the unpacked directory../configure --program-suffix=213make clean all; sudo make install
libIDL-0.8
libIDL-0.8 ends up having three dependencies beyond software installed by Xcode, so we will build and install from the dependencies upward.
pkg-config
pkg-config has no external dependencies.
- Download the latest... and unpack.
