Mercurial > sdl-ios-xcode

comparison README.MacOSX @ 1006:3d9a199d2a70

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated SDL for MacOS X Xcode support
author Sam Lantinga <slouken@libsdl.org>
date Mon, 06 Dec 2004 04:17:56 +0000
parents ae4ab3ac89a9
children f12379c41042
comparison
equal deleted inserted replaced
1005:2ab1cb02a44e 1006:3d9a199d2a70
5 These instructions are for people using Apple's Mac OS X (pronounced 5 These instructions are for people using Apple's Mac OS X (pronounced
6 "ten"). 6 "ten").
7 7
8 From the developer's point of view, OS X is a sort of hybrid Mac and 8 From the developer's point of view, OS X is a sort of hybrid Mac and
9 Unix system, and you have the option of using either traditional 9 Unix system, and you have the option of using either traditional
10 command line tools or Apple's IDE ProjectBuilder (PB). 10 command line tools or Apple's IDE Xcode.
11 11
12 To build SDL using the command line, use the standard configure and make 12 To build SDL using the command line, use the standard configure and make
13 process: 13 process:
14 14
15 ./configure 15 ./configure
91 variations of them) in Exult and ScummVM; both are available in source on 91 variations of them) in Exult and ScummVM; both are available in source on
92 the net, so feel free to take a peek at them for inspiration! 92 the net, so feel free to take a peek at them for inspiration!
93 93
94 94
95 ============================================================================== 95 ==============================================================================
96 Using the Simple DirectMedia Layer with Project Builder 96 Using the Simple DirectMedia Layer with Xcode
97 ============================================================================== 97 ==============================================================================
98 98
99 These instructions are for using Apple's Project Builder IDE to build SDL 99 These instructions are for using Apple's Xcode IDE to build SDL applications.
100 applications.
101 100
102 - First steps 101 - First steps
103 102
104 The first thing to do is to unpack the PBProjects.tar.gz archive in the 103 The first thing to do is to unpack the Xcode.tar.gz archive in the
105 top level SDL directory (where the PBProjects.tar.gz archive resides). 104 top level SDL directory (where the Xcode.tar.gz archive resides).
106 Because Stuffit Expander will unpack the archive into a subdirectory, 105 Because Stuffit Expander will unpack the archive into a subdirectory,
107 you should unpack the archive manually from the command line: 106 you should unpack the archive manually from the command line:
108 cd [path_to_SDL_source] 107 cd [path_to_SDL_source]
109 tar zxf PBProjects.tar.gz 108 tar zxf Xcode.tar.gz
110 This will create a new folder called PBProjects, which you can browse 109 This will create a new folder called Xcode, which you can browse
111 normally from the Finder. 110 normally from the Finder.
112 111
113 - Building the Framework 112 - Building the Framework
114 113
115 The SDL Library is packaged as a framework bundle, an organized 114 The SDL Library is packaged as a framework bundle, an organized
118 framework as a more user and system-friendly shared library, whose library 117 framework as a more user and system-friendly shared library, whose library
119 file behaves more or less like a standard UNIX shared library. 118 file behaves more or less like a standard UNIX shared library.
120 119
121 To build the framework, simply open the framework project and build it. 120 To build the framework, simply open the framework project and build it.
122 By default, the framework bundle "SDL.framework" is installed in 121 By default, the framework bundle "SDL.framework" is installed in
123 ~/Library/Frameworks. Therefore, the testers and project stationary expect 122 /Library/Frameworks. Therefore, the testers and project stationary expect
124 it to be located there. However, it will function the same in any of the 123 it to be located there. However, it will function the same in any of the
125 following locations: 124 following locations:
126 125
127 ~/Library/Frameworks 126 ~/Library/Frameworks
128 /Local/Library/Frameworks 127 /Local/Library/Frameworks