Mac: Fixed markdown formatting in README.
authorPhilipp Wiesemann <philipp.wiesemann@arcor.de>
Wed, 21 Sep 2016 23:07:08 +0200
changeset 10361de0c0d037e71
parent 10360 2e78b92aa9b3
child 10362 070fe7c1fc85
Mac: Fixed markdown formatting in README.

The newlines were lost in doxygen output.
docs/README-macosx.md
     1.1 --- a/docs/README-macosx.md	Wed Sep 21 23:06:49 2016 +0200
     1.2 +++ b/docs/README-macosx.md	Wed Sep 21 23:07:08 2016 +0200
     1.3 @@ -11,9 +11,9 @@
     1.4  To build SDL using the command line, use the standard configure and make
     1.5  process:
     1.6  
     1.7 -	./configure
     1.8 -	make
     1.9 -	sudo make install
    1.10 +    ./configure
    1.11 +    make
    1.12 +    sudo make install
    1.13  
    1.14  You can also build SDL as a Universal library (a single binary for both
    1.15  32-bit and 64-bit Intel architectures), on Mac OS X 10.7 and newer, by using
    1.16 @@ -22,8 +22,8 @@
    1.17      mkdir mybuild
    1.18      cd mybuild
    1.19      CC=$PWD/../build-scripts/gcc-fat.sh CXX=$PWD/../build-scripts/g++fat.sh ../configure
    1.20 -	make
    1.21 -	sudo make install
    1.22 +    make
    1.23 +    sudo make install
    1.24  
    1.25  This script builds SDL with 10.5 ABI compatibility on i386 and 10.6
    1.26  ABI compatibility on x86_64 architectures.  For best compatibility you
    1.27 @@ -86,12 +86,12 @@
    1.28  To get this build automatically, add something like the following rule to
    1.29  your Makefile.am:
    1.30  
    1.31 -bundle_contents = APP_NAME.app/Contents
    1.32 -APP_NAME_bundle: EXE_NAME
    1.33 -	mkdir -p $(bundle_contents)/MacOS
    1.34 -	mkdir -p $(bundle_contents)/Resources
    1.35 -	echo "APPL????" > $(bundle_contents)/PkgInfo
    1.36 -	$(INSTALL_PROGRAM) $< $(bundle_contents)/MacOS/
    1.37 +    bundle_contents = APP_NAME.app/Contents
    1.38 +    APP_NAME_bundle: EXE_NAME
    1.39 +    	mkdir -p $(bundle_contents)/MacOS
    1.40 +    	mkdir -p $(bundle_contents)/Resources
    1.41 +    	echo "APPL????" > $(bundle_contents)/PkgInfo
    1.42 +    	$(INSTALL_PROGRAM) $< $(bundle_contents)/MacOS/
    1.43  
    1.44  You should replace EXE_NAME with the name of the executable. APP_NAME is what
    1.45  will be visible to the user in the Finder. Usually it will be the same
    1.46 @@ -105,13 +105,13 @@
    1.47  If you want the created bundles to be installed, you may want to add this
    1.48  rule to your Makefile.am:
    1.49  
    1.50 -install-exec-hook: APP_NAME_bundle
    1.51 -	rm -rf $(DESTDIR)$(prefix)/Applications/APP_NAME.app
    1.52 -	mkdir -p $(DESTDIR)$(prefix)/Applications/
    1.53 -	cp -r $< /$(DESTDIR)$(prefix)Applications/
    1.54 +    install-exec-hook: APP_NAME_bundle
    1.55 +    	rm -rf $(DESTDIR)$(prefix)/Applications/APP_NAME.app
    1.56 +    	mkdir -p $(DESTDIR)$(prefix)/Applications/
    1.57 +    	cp -r $< /$(DESTDIR)$(prefix)Applications/
    1.58  
    1.59  This rule takes the Bundle created by the rule from step 3 and installs them
    1.60 -into $(DESTDIR)$(prefix)/Applications/.
    1.61 +into "$(DESTDIR)$(prefix)/Applications/".
    1.62  
    1.63  Again, if you want to install multiple applications, you will have to augment
    1.64  the make rule accordingly.
    1.65 @@ -126,11 +126,16 @@
    1.66     unless you also install SDL on that other computer. A good solution
    1.67     for this dilemma is to static link against SDL. On OS X, you can
    1.68     achieve that by linking against the libraries listed by
    1.69 -     sdl-config --static-libs
    1.70 +
    1.71 +       sdl-config --static-libs
    1.72 +
    1.73     instead of those listed by
    1.74 -     sdl-config --libs
    1.75 +
    1.76 +       sdl-config --libs
    1.77 +
    1.78     Depending on how exactly SDL is integrated into your build systems, the
    1.79     way to achieve that varies, so I won't describe it here in detail
    1.80 +
    1.81  2) Add an 'Info.plist' to your application. That is a special XML file which
    1.82     contains some meta-information about your application (like some copyright
    1.83     information, the version of your app, the name of an optional icon file,
    1.84 @@ -156,8 +161,10 @@
    1.85  top level SDL directory (where the Xcode.tar.gz archive resides).
    1.86  Because Stuffit Expander will unpack the archive into a subdirectory,
    1.87  you should unpack the archive manually from the command line:
    1.88 -	cd [path_to_SDL_source]
    1.89 -	tar zxf Xcode.tar.gz
    1.90 +
    1.91 +    cd [path_to_SDL_source]
    1.92 +    tar zxf Xcode.tar.gz
    1.93 +
    1.94  This will create a new folder called Xcode, which you can browse
    1.95  normally from the Finder.
    1.96