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
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
|
Building Enigma under MacOS X 10.6, 10.5, and 10.4
Overview:
---------
Due to which machines are available to Enigma developers, the latest
version of Enigma has only been built under MacOS X 10.6. The
instructions for building should apply identically under 10.4 and 10.5.
The latest SDL library package no longer supports earlier versions of
Mac OS and so Enigma has dropped support for 10.3 or earlier.
Note that even though the build process is not run under Xcode,
it does require that Xcode, which includes a number of developer tools,
has been installed on the build machine.
Enigma is built from the command line using make. There is a make
target that will create a Mac OS application bundle in a compressed
disk image file, enigma.dmg. That file can be copied to a Mac without
any special runtime environment having to be installed, and the Enigma
app simply dropped into a folder to be ready to run. The following
instructions allow you to build a universal binary that will run
on both PowerPc and Intel Macs running MacOS 10.4 or later.
You do need some other packages installed in order to build Enigma on
your MacOS X system. Earlier versions of this README used packages
installed from Macports. That is no longer necessary. These instructions
have you install packages in /usr/local. It is possible for libraries in
that directory to conflict with other version of the same library that
have been installed by Macports in its default /opt/local directory.
If you normally use Macports, it may be advisable to temporarily rename
/opt/local and your current /usr/local to get them out of the way,
install your Enigma build environment in a fresh /usr/local, then
rename that to something like /usr/local-enigma to save it for the next
time you need to build Enigma, restoring the original /opt/local and /usr/local.
One step in the build process uses the program mkalias which is part of osxutils,
a package that can be downloaded from http://sourceforge.net/projects/osxutils/
under the terms of the GNU GPL. It installs into /usr/local. If you are
using a special version of /usr/local for the Enigma build, be sure to install
osxutils after you have switched to that /usr/local.
Step 0: Create a text file to contain a shell script that you will use to
build universal binaries that will work for MacOS 10.4, 10.5, and 10.6.
You can name the file whatever you like, but in this README it will be
referred to as builduniversal.sh. Place it somewhere convenient such as
in a ~/bin directory. If you place it there and make ~/bin part of your PATH,
you can refer to builduniversal.sh just by name in command lines and scripts.
If you don't place it in your PATH make sure that you use the full path name
wherever there is a command in the following that just says builduniversal.sh.
Here are the contents of builduniversal.sh:
#!/bin/sh
# build a package for universal 10.4+ if it is configured in standard way
# does the configure but not the make or make install
# You can add arguments to be passed to configure
# You can pass in prefix values in CFLAGS, CXXFLAGS, LDFLAGS environment variables
MACOSX_DEPLOYMENT_TARGET=10.4 \
UNIFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4 -arch i386 -arch ppc" \
CC=/usr/bin/gcc-4.0 \
CXX=/usr/bin/g++-4.0 \
CFLAGS="$CFLAGS $UNIFLAGS" \
CXXFLAGS="$CXXFLAGS $UNIFLAGS" \
LDFLAGS="$LDFLAGS $UNIFLAGS -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk" \
./configure --disable-dependency-tracking $*
Step 0b: You must make sure that the following is executed in any shell that you
use during the build process. Either type this at the command line when you open
a shell or put it in your ~/.profile file so it is executed automatically when you
open a command line shell
export MACOSX_DEPLOYMENT_TARGET=10.4
Step 1. Download the required SDL 1.2.x libraries and related packages. At each
of the following web pages you will find both a prebuilt binary framework
for MacOS X in the form of a .dmg file, and the sources in the form of a
compressed tar file (tar.gz, also called a 'tarball'). You will need to download both of
those for each of the four packeges listed below. Note that there is a version 1.3.x
of SDL that Enigma does not support. You need SDL 1.2.14, which is the last
to be released in the 1.2. series. The other packages have their own version numbers.
SDL http://www.libsdl.org/
SDL_image http://www.libsdl.org/projects/SDL_image/
SDL_ttf http://www.libsdl.org/projects/SDL_ttf/
SDL_mixer http://www.libsdl.org/projects/SDL_mixer/
Step 2: For each of the four .dmg files downloaded in Step 1, double click
the dmg file to open it in the Finder, then drag the Framework folder that is revealed
into the /Library/Frameworks folder. Note that the system may ask you to enter
your password to authenticate yourself as an administrator. We will use the
four tarballs of source code you downloaded in a later step.
Step 3: Download the source tarballs of the following libraries from the
web sites that are indicated. In each case download the latest stable version.
libjpeg http://www.ijg.org/
libpng http://www.libpng.org/pub/png/libpng.html
xerces-c http://xerces.apache.org/xerces-c/build-3.html
gettext http://www.gnu.org/software/gettext/#TOCdownloading
Step 5. Unpack each of the source tarballs in any convenient directory.
Each will go into its own subdirectory, as the tarballs are set up that way.
Step 6: Install the SDL library. This is the trickiest one to build as it requires a
special build script that is downloaded from a bug report about SDL. The steps to build it:
Step 6a. Download the build script to some convenient directory.
This command will get the file, naming it fatbuild.sh in the
current directory.
curl -o fatbuild.sh "http://bugzilla.libsdl.org/attachment.cgi?id=453"
Step 6b. Copy the downloaded fatbuild.sh file to the build-scripts
subdirectory of the unpacked SDL sources, replacing the original one that is there,
then cd to the sources directory. For example,
cp fatbuild.sh SDL-1.2.14/build-scripts/
cd SDL-1.2.14
Step 6c: Build SDL using the following commands. The export command doesn't have to
be repeated if you remembered to do it as mentioned in Step 0b.
export MACOSX_DEPLOYMENT_TARGET=10.4
build-scripts/fatbuild.sh
sudo build-scripts/fatbuild.sh install
Step 7. Install each of the other seven packages that you downloaded source tarballs for
by unpacking them (each will go into its own subdirectory), cd to its directory,
and run the commands (assuming you have placed builduniversal.sh in your PATH)
builduniversal.sh
make
sudo make install
Step 8. Install ImageMagick, which is needed to generate the documentation
during the build process. ImageMagick will not be part of Enigma, so it does not
have to built as a universal binary as long as it can run on the build computer.
To build it, download the current sources of ImageMagick from
ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick.tar.gz
untar it into a convenient directory, cd to it, and build with the commands
./configure
make
sudo make install
Step 9. Build Enigma:
Important: The configure step requires you to be logged in with access
to the window system, i.e., either at the Mac keyboard or using remote
screen sharing, and in a Terminal.app comand line. It will hang trying
to test the SDL library if you are using ssh to log in remotely with no
GUI screen.
Remember to perform Step 0b each time you open a new Termnal.app window.
Then cd to the Enigma directory tree and
run the following commands which make use of the builduniversal.sh
script file that was listed in step 0 and is assumed to be in your PATH
Important: If you have built in the Enigma directory tree before and
made some change to the build environment, use make distclean to ensure
that there are no files from the old build interfering with the new build
./autogen.sh
CFLAGS="-I/usr/local/include" CXXFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" builduniversal.sh
make gmo
make
make macapp
That's it! If it all works, there will be a copy of enigma.dmg in the
etc/ subdirectory and a copy of Enigma.app in etc/macfiles/
subdirectory.
|
