Changes between Version 1 and Version 2 of MacBuildInstructions


Ignore:
Timestamp:
Feb 23, 2011, 8:53:36 AM (13 years ago)
Author:
Kieran P
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MacBuildInstructions

    v1 v2  
    55First you'll need to install XCode. The tools installed with it include the compilers you'll need to compile the game and the libraries it depends on.
    66
    7 You can obtain XCode from http://developer.apple.com/technologies/xcode.html
    8 
    9 You'll need a Mac Dev account, but registration and download is free.
     7You can obtain XCode from http://developer.apple.com/technologies/xcode.html . You'll need a Mac Dev account, but registration and download is free.
    108
    119Once downloaded, double click the file and follow the installation instructions.
     
    1311== Step 2: Install Homebrew ==
    1412
    15 Homebrew, a package management tool for Mac, is far superior to it's predecessors (like MacPorts and FinkCommander).
    16 
    17 It's lightweight, and very fast, and the preferred package management tool. If you use MacPorts or FinkCommander, you're on your own, since the content below will focus on using Homebrew to compile the game.
     13Homebrew, a package management tool for Mac, is far superior to it's predecessors (like MacPorts and FinkCommander). It's lightweight, and very fast, and the preferred package management tool. If you use MacPorts or FinkCommander, you're on your own, since the content below will focus on using Homebrew to compile the game.
    1814
    1915To install, follow the instructions at https://github.com/mxcl/homebrew/wiki/installation , but skip the step about installing XCode, as you did that above.
    2016
    21 This guide assumes you installed Homebrew to /usr/local, and not /opt or any other prefix, and that you didn't use sudo. If you installed in a non-standard place or used sudo, you're on your own.
     17The rest of this guide assumes you installed Homebrew to /usr/local, not to /opt or any other non-standard prefix, and that you didn't use sudo. If you installed otherwise, you're on your own.
    2218
    2319== Step 3: Install 0 A.D. Dependencies ==
    2420
    25 Coming soon
     21Run the following in a console to install the dependencies needed for 0 A.D. Installing all dependencies takes anywhere between '''40 minutes up to as much as 2 hours''', during which time, the computer is pretty slow, so be patient with it. Best to do it when you won't be using the computer while it's installing.
     22
     23{{{
     24brew install subversion boost libxml2 cmake enet sdl libogg libvorbis nasm devil curl
     25brew link libxml2
     26brew link curl
     27}}}
     28
     29== Step 4: Obtaining the 0 A.D. source ==
     30
     31If you want to grab the release files, you can do that. But in this guide, we'll compile SVN, which has the newest features.
     32
     33'''COMING SOON'''
     34
     35== Step 5: Preparing 0 A.D. to compile ==
     36
     37Atlas, the unit, building, and map editor used by 0 A.D. isn't compatible with Mac, so there is a special step required to get the game to compile.
     38
     39Open up build/workspaces/update_workspaces.sh in a text editor and remove the text "--atlas" from the last line. Remove only that text (not the whole line or anything else on that line).
     40
     41== Step 6: Compiling 0 A.D. ==
     42
     43Finally, to compile, run the following commands in a console (adjust the path on the first line to go to the actual directory source root):
     44
     45{{{
     46cd /path/to/source
     47cd build/workspaces
     48./update-workspaces.sh
     49cd gcc
     50make CONFIG=Release
     51}}}
     52
     53== Step 7: Running 0 A.D. ==
     54
     55To run the game, run the following commands in a console:
     56
     57{{{
     58cd /path/to/source
     59cd binaries/system
     60./pyrogenesis
     61}}}