Mercurial > sdl-ios-xcode
diff README.MacOSX @ 1006:3d9a199d2a70
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 |
line wrap: on
line diff
--- a/README.MacOSX Sat Dec 04 20:53:58 2004 +0000 +++ b/README.MacOSX Mon Dec 06 04:17:56 2004 +0000 @@ -7,7 +7,7 @@ From the developer's point of view, OS X is a sort of hybrid Mac and Unix system, and you have the option of using either traditional -command line tools or Apple's IDE ProjectBuilder (PB). +command line tools or Apple's IDE Xcode. To build SDL using the command line, use the standard configure and make process: @@ -93,21 +93,20 @@ ============================================================================== -Using the Simple DirectMedia Layer with Project Builder +Using the Simple DirectMedia Layer with Xcode ============================================================================== -These instructions are for using Apple's Project Builder IDE to build SDL -applications. +These instructions are for using Apple's Xcode IDE to build SDL applications. - First steps -The first thing to do is to unpack the PBProjects.tar.gz archive in the -top level SDL directory (where the PBProjects.tar.gz archive resides). +The first thing to do is to unpack the Xcode.tar.gz archive in the +top level SDL directory (where the Xcode.tar.gz archive resides). Because Stuffit Expander will unpack the archive into a subdirectory, you should unpack the archive manually from the command line: cd [path_to_SDL_source] - tar zxf PBProjects.tar.gz -This will create a new folder called PBProjects, which you can browse + tar zxf Xcode.tar.gz +This will create a new folder called Xcode, which you can browse normally from the Finder. - Building the Framework @@ -120,7 +119,7 @@ To build the framework, simply open the framework project and build it. By default, the framework bundle "SDL.framework" is installed in -~/Library/Frameworks. Therefore, the testers and project stationary expect +/Library/Frameworks. Therefore, the testers and project stationary expect it to be located there. However, it will function the same in any of the following locations: