Now it's time to get the source.

First get mercurial form:
http://mercurial.selenic.com/downloads/

Now get murky which gives you a visual client to work with. It's not perfect and at the moment there seems to be an issue getting it to work with OS X certificates (as so ssl doesn't work through murky). That's ok, just use the terminal when pushing and pulling to/from the server.

To get a copy out of source forge, you can use murky (read only isn't ssl), where you clone from the source:
http://gamestool.hg.sourceforge.net:800 … /gamestool

To push your changes to the server, you'll need to login to source forge to get the SSL location.

Now it's time for some of 3rd party includes. Don't worry, this walkthrough is going into the READ_ME which at this point isn't very good.

To get boost, you'll need to download from their homepage:
http://www.boost.org/users/download/

unzip and now comes the fun part:
This guy here posted the method I used and it seems to work:
http://stackoverflow.com/a/11297605
I'll paraphrase the post here:

Configure (and build bjam):

 $ ./bootstrap.sh --prefix=/some/dir/you/would/like/to/prefix 

Build:

$ ./b2

Install:

$ ./b2 install

Now you'll need to sudo the install because it'll want to put the dynamic libs into /usr/lib which is a locked system dir.
I also install into /usr/include to make things easy.

To get the google testing, go here:
http://code.google.com/p/googletest/downloads/list

Now extract it somewhere sensible (I put mine in /Developer/SDKs/gtest-1.6.0). Next you have to build the static lib that gets included in our unit test projects. So crack open the README and follow the instructions to build it. This will normally involve the cmake function you got when you installed gcc in the above step. I say normally because in windows you open the Visual Studio solution included with the google test download.

Anyway, you should get a libgtest.a file inside the lib directory. Next you may need to point you projects to this location, and to do this I like to add symbolic links (shortcuts) in the 'shared' directory of the gamestool project directory. This directory is included by the specific eclipse projects that need them. This seems neater than distributing assumed directory locations in the project itself and makes it easier for people to change where the project looks for different SDKs and frameworks.