Difference between revisions of "HOWTO get ns-3 running on Mac OS X (10.6.2 Intel)"
|Line 47:||Line 47:|
Revision as of 17:39, 20 March 2010
The installation instructions included in this page are not meant to be comprehensive and represent only one of the many ways of getting ns-3 to build in a Snow Leopard Mac OS X system. Commands (>>) should be run from a Terminal window. Mac OS X does not support all of the features of ns-3, but core functionality is provided. Check http://www.nsnam.org/wiki/index.php/Installation for further details on what is and what is not supported on Mac OS X.
1) Install XCode
You will find XCode in the Mac OS X Install DVD that came with your Mac. Alternatively, you can download the most recent version of XCode from the Apple Developer Connection website (http://developer.apple.com/mac/). The XCode development environment includes the gcc compiler and critical libraries required to build applications to be run in Mac OS X.
2) Install Fink
2.1) Download Fink source release version 0.29.10 from http://downloads.sourceforge.net/fink/fink-0.29.10.tar.gz
2.2) Extract the contents of the file and enter open up the Terminal in the resulting folder.
2.3) Install Fink (during the interactive installation process, select the 32 bit installation).
2.4) Execute a script in order to setup the environment variables for Fink.
>> /sw/bin/pathsetup.sh (assuming a default install folder).
2.5) Install updated packages, if available.
>> fink selfupdate
Note that you can use also MacPorts (http://www.macports.org/) instead of Fink. It's really a matter of your personal choice.
3) Install Mercurial
Download and install Mercurial from http://mercurial.selenic.com/wiki/Download Choose the latest binary package. Either you can choose to install mercurial trough MacPorts or Fink, but make sure to have a recent version (1.4.2 or better)
4) Download source code
>> hg clone http://code.nsnam.org/ns-3-allinone
>> cd ns-3-allinone
5) Build the local repository
6) Test the installation
>> cd ns-3-dev
There is a known bug involving -arch directive. If you get an error about linking and object architecture mismatch, check if you have an environment variable "CFLAGS=-arch i386" or similar. If you do, try disabling it.