Smokin' Guns Mac 1.0 was built on iBook G4 running Mac OS X 10.4 (Tiger). It was originally tested on 10.4.11 and 10.5.6 on both PowerPC and Intel platforms. It has been tested to build correctly on 10.5 (Leopard) as well, but not yet on 10.6 (Snow Leopard).
You need XCode 2.5, 3.0, or 3.1 installed. It is available for free at the Apple Developer Connection
1.) Download Smokin' Guns 1.0 "Generic" Zip Archive from a download mirror
2.) Download XCode (2.5, 3.1, or newer) from
http://connect.apple.com or use (for now) the copy that is available on your Mac OS X installation DVD in Optional Installs
3.) Download MacPorts (1.7.1 or newer) from
http://www.macports.org/4.) Download SDL 1.2 Mac OS X Runtime (DMG) and Source Code (GZ) from
http://www.libsdl.org/5.) Install XCode (2.5 or newer)
6.) Install MacPorts (1.7.1 or newer)
7.) Open Terminal from Applications -> Utilities
8.) Navigate into your Downloads directory with 'cd Downloads'
9.) Checkout a fresh copy of the 1.1 engine source code from svn by typing
- Code: Select all
svn co https://smokinguns.svn.sourceforge.net/svnroot/smokinguns/branches/1.1/ sg11-engine
where sg11-engine is the destination directory to be created
10.) Type
- Code: Select all
sudo port install pkg-config libsdl
11.) Extract SDL by typing
- Code: Select all
tar -xzf SDL-1.2.13.tar.gz
12.) Navigate into the newly created SDL directory and type
- Code: Select all
./configure
then
- Code: Select all
make
and finally
- Code: Select all
sudo make install
13.) You can now navigate back a level by typing
- Code: Select all
cd ..
where you will then enter the sg11-engine directory with
- Code: Select all
cd sg11-engine
14.) Start the build process by typing
- Code: Select all
./make-macosx-ub.sh
15.) Generated files if compilation succeeds will appear in Build
16.) Navigate back a level again via the same method, where you will end up in Downloads again.
17.) Extract your SG Generic zip with the command
- Code: Select all
unzip Smokin_Guns_1.0.zip
18.) You can open a Finder window and navigate to Downloads -> sg11-engine -> build -> release-darwin-ub to find the application bundle which you'd want to ctrl + click (or right) and then Show Contents of, then drilling down until you're inside Contents -> MacOS -> baseq3.
19.) Open a second Finder window with cmd + n hotkey and navigate to Downloads -> Smokin' Guns -> smokinguns
20.) Drag and drop the pk3 and cfg files from the unpacked generic area mentioned in 19 into the place indicated in step 18
21.) Make modifications to your baseq3/*.cfg files with textedit or other editor if applicable (Widescreen users, those with 3D glasses)
22.) Try and start the game (Assuming the thing we call a bundle has the correct icon, that is what to click..)
My apologies for not checking against build steps for errors, but I have only one Mac and am using SL. Please help me improve the quality of this guide if you find problems and have gotten it to work.
Notes:
You could install SDL from MacPorts, but it would draw more dependencies, and wouldn't mesh as well with the environment.
Using the Framework alone instead of compiling from source should be enough, and is as simple as dragging and dropping the Directory.Framework folder from a Finder window into /Library/Frameworks. This will not be detected on SL, but as I recall works on Tiger and Leopard.
Since SDL does not build due to QD depreciation, a binary build of the pkg-config files that are build from gzip compressed source (Not the framework) may in fact be necessary for a faithful build. We do ship a dylib, which is used in linking, but no promises it'll be fully functional. Build on 10.3.9 to 10.5 for now if you can help it.
A workaround to some build problems is to remove the ppc sections of the make-macosx-ub.sh file, and build each binary if you have hardware access on the native target platform, later using the lipo(1) tool to rejoin the pieces. While SL does not support PPC, one could join a 10.5 built PPC binary with a 10.6 i386 binary to create a production mach-o multi-arch bundle.
Since I haven't had time to fix the script, you can simply move out SDKs you don't want the program built against them, but there's no point since the build at this time would only need you to do this on SL, which is broken upstream. Don't fret, 10.4/10.5 binaries work on SL, and you can reuse my package once I get it back up, simply replacing a few files if you want the fresh.