-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.MacOSX
111 lines (93 loc) · 5.87 KB
/
README.MacOSX
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
BZFlag README for Mac OS X
==========================
BZFlag is fully supported on Mac OS X. Included below are instructions on
installing BZFlag both from a binary and from a released source distribution.
Binary Distribution
-------------------
See the project site downloads of BZFlag for Mac OS X at
http://sourceforge.net/projects/bzflag/files/bzflag%20Mac%20OS%20X to obtain
the latest binary distribution.
Once you've obtained a binary distribution of BZFlag, installation should be a
simple matter of copying the icon provided in the disk mounting image (the
.dmg) to your Applications folder. If you cannot run the client at all
(e.e. it starts to a black screen, or the icon bounces but then nothing
happens), you can try several things:
1) Move or delete the BZFlag directory in your personal application support
folder at ~/Library/Application Support/BZFlag. As of Mac OS X 10.7, the
~/Library directory is hidden by default. You can open it by navigating
to your home directory, entering the Command-Shift-G key sequence, then
typing "Library" and clicking "Go." Note that this directory contains
your saved configuration, screenshots, and map files, so you may want to
move or delete only your configuration directory (stored in the directory
with the BZFlag version number).
2) Check your console for error messages. Open your console application at
/Utilities/Console.app, and expand the "User Diagnostic Reports" list in
the sidebar under "Diagnostic and Usage Information." Any crash reports
should be listed there and will start with "BZFlag."
3) Run the binary directly by using Terminal:
/Applications/BZFlag-#.#.#.app/Contents/MacOS/BZFlag-#.#.#
(replace "#.#.#" with your actual BZFlag version number)
Source Distribution
-------------------
You can build BZFlag from source using Xcode version 4.2 and later. As of
BZFlag version 2.4.3 BZFlag has a fully native Xcode project
file. The earlier method of using the Xcode project file as a wrapper for
autotools is no longer supported. If you have a version of Xcode which
includes autotools, or have installed autotools yourself, you may additionally
be able to build using the traditional autotools method. See the README file
for further information. You will still need to install the SDL framework as
detailed below.
To build BZFlag using Xcode, download the latest version of SDL 1.2 from
http://www.libsdl.org/download-1.2.php (you want the "Mac OS X" link for your
operating system version under "Runtime Libraries"). For Mac OS X 10.6, the
recommended SDL version is 1.2.13. Mount the disk image and place the file
"SDL.framework" in your /Library/Frameworks directory (an administrator's
account may be required). Obtain the latest BZFlag source archive from
GitHub at https://github.com/BZFlag-Dev/bzflag (you want the .tar.gz or .tar.bz2
archive, NOT the .zip archive) or from the subversion repository using the
instructions at http://wiki.bzflag.org/SVN. Once you have obtained the source
code, open the BZFlag.xcodeproj file located in the Xcode/ directory.
The default behavior is to build a debug client. If you want a standard
client, click the "BZFlag" scheme button at the top left corner of the screen,
scroll down, and click "Edit Scheme..." at the bottom of the pop-up menu. In
the left sidebar, click the Run phase, and in the right area select the
Info tab. Under Build Configuration, select the desired scheme of Debug or
Release.
To build the client, select Build from the Product menu or enter the Command-B
key sequence. Note that the BZFlag version is no longer automatically
appended to the build product.
NOTE: You may encounter the error "Unknown option
-NSDocumentRevisionsDebugMode" due to a deficiency in Xcode that prevents us
from permanently disabling a certain setting. If you do encounter this error,
click the "BZFlag" scheme button, click "Edit Scheme..." and under the "Options"
tab, deselect "Allow debugging when using document Versions Browser" before
running the client straight from Xcode.
If the build was successful, you can run the application from Xcode selecting
the Product menu and clicking Run or by entering the Command-R key sequence.
You will also want to locate the application you just built. Make sure the
Navigator pane is visible and select the Project Navigator, then expand the
"BZFlag" project container and the "Targets" group within it. Click the
"BZFlag.app" target. Make sure the Utilities pane is visible, and under
the Identity and Type panel it will show the full path to the application.
Click the small grey right arrow at the bottom right corner of the path to
reveal the application in the Finder.
NOTICE: If you're compiling from source, it is expected that you have
sufficient/proficient understanding of how to compile applications on the
command line or using XCode and how to perform compilation troubleshooting
without assistance. This holds particularly true for all alpha/beta testing
releases as well as for any sources pulled directly from the Subversion source
repository checkout. If you have problems building from a checkout, you should
try building from an official release that we have posted to SourceForge to
see if you can duplicate the issue, and then ask us for assistance.
Usage
-----
To install BZFlag, copy the application you obtained as a binary distribution
or built from source into your /Applications directory, or use it from another
location of your choice. Different client versions may exist simultaneously on
any system without issue.
To access the bzadmin text client or the bzflag server bzfs, right click the
application, click "Show Package Contents," and navigate to Contents/MacOS.
Server plugins are located at Contents/PlugIns. Note that while the plugin
names are different from Windows and Linux (something like "libname.dylib"
instead of "name.dll or "name.so"), bzfs will still load them when you specify
the full plugin path.