README.MacOSX
changeset 6987 7084af936d82
parent 1839 78da406ad139
     1.1 --- a/README.MacOSX	Sat Mar 09 10:35:12 2013 -0800
     1.2 +++ b/README.MacOSX	Sun Mar 10 09:03:38 2013 -0700
     1.3 @@ -56,7 +56,7 @@
     1.4  name as specified in your configure.in file.
     1.5  
     1.6  If your project builds more than one application, you will have to do a bit
     1.7 -more.  For each of your target applications, you need a seperate rule.
     1.8 +more. For each of your target applications, you need a separate rule.
     1.9  
    1.10  If you want the created bundles to be installed, you may want to add this
    1.11  rule to your Makefile.am:
    1.12 @@ -75,13 +75,13 @@
    1.13  
    1.14  But beware! That is only part of the story! With the above, you end up with
    1.15  a bare bone .app bundle, which is double clickable from the Finder. But
    1.16 -there are some  more things you should do before shipping yor product...
    1.17 +there are some more things you should do before shipping your product...
    1.18  
    1.19  1) The bundle right now probably is dynamically linked against SDL. That 
    1.20     means that when you copy it to another computer, *it will not run*,
    1.21     unless you also install SDL on that other computer. A good solution
    1.22     for this dilemma is to static link against SDL. On OS X, you can
    1.23 -   achieve that by linkinag against the libraries listed by
    1.24 +   achieve that by linking against the libraries listed by
    1.25       sdl-config --static-libs
    1.26     instead of those listed by
    1.27       sdl-config --libs
    1.28 @@ -120,7 +120,7 @@
    1.29  - Building the Framework
    1.30  
    1.31  The SDL Library is packaged as a framework bundle, an organized
    1.32 -relocatable folder heirarchy of executible code, interface headers, 
    1.33 +relocatable folder hierarchy of executable code, interface headers,
    1.34  and additional resources. For practical purposes, you can think of a 
    1.35  framework as a more user and system-friendly shared library, whose library
    1.36  file behaves more or less like a standard UNIX shared library.
    1.37 @@ -162,11 +162,11 @@
    1.38  
    1.39  - Building from command line
    1.40      Use pbxbuild in the same directory as your .pbproj file
    1.41 -         
    1.42 +
    1.43  - Running your app
    1.44      You can send command line args to your app by either invoking it from
    1.45      the command line (in *.app/Contents/MacOS) or by entering them in the
    1.46 -    "Executibles" panel of the target settings.
    1.47 +    "Executables" panel of the target settings.
    1.48      
    1.49  - Implementation Notes
    1.50      Some things that may be of interest about how it all works...
    1.51 @@ -181,6 +181,6 @@
    1.52          You are free to modify your Cocoa app with generally no consequence 
    1.53          to SDL. You cannot, however, easily change the SDL window itself.
    1.54          Functionality may be added in the future to help this.
    1.55 -	
    1.56 +
    1.57  
    1.58  Known bugs are listed in the file "BUGS"