encounter
/
SDL
mirror of https://github.com/encounter/SDL.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: Modernized README-macosx.md and cleaned up the Markdown a little. 

Reference #960.
This commit is contained in:
Ryan C. Gordon 2021-11-09 10:50:18 -05:00
parent 0f2bf62935
commit cfdbd6acca
No known key found for this signature in database
GPG Key ID: FA148B892AB48044
1 changed files with 281 additions and 240 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

251
docs/README-macosx.md
View File

@ -1,60 +1,75 @@
Mac OS X # Mac OS X (aka macOS).
==============================================================================
These instructions are for people using Apple's Mac OS X (pronounced These instructions are for people using Apple's Mac OS X (pronounced
"ten"). "ten"), which in newer versions is just referred to as "macOS".
From the developer's point of view, OS X is a sort of hybrid Mac and From the developer's point of view, macOS is a sort of hybrid Mac and
Unix system, and you have the option of using either traditional Unix system, and you have the option of using either traditional
command line tools or Apple's IDE Xcode. command line tools or Apple's IDE Xcode.
Command Line Build # Command Line Build
==================
To build SDL using the command line, use the standard configure and make To build SDL using the command line, use the standard configure and make
process: process:
./configure ```bash
make mkdir build
sudo make install cd build
../configure
make
sudo make install
```
CMake is also known to work, although it continues to be a work in progress:
```bash
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
sudo make install
```
You can also build SDL as a Universal library (a single binary for both You can also build SDL as a Universal library (a single binary for both
32-bit and 64-bit Intel architectures), on Mac OS X 10.7 and newer, by using 64-bit Intel and ARM architectures), by using the build-scripts/clang-fat.sh
the gcc-fat.sh script in build-scripts: script.
mkdir mybuild ```bash
cd mybuild mkdir build
CC=$PWD/../build-scripts/gcc-fat.sh CXX=$PWD/../build-scripts/g++-fat.sh ../configure cd build
make CC=$PWD/../build-scripts/clang-fat.sh ../configure
sudo make install make
sudo make install
```
This script builds SDL with 10.5 ABI compatibility on i386 and 10.6 This script builds SDL with 10.6 ABI compatibility on 64-bit Intel and 11.0
ABI compatibility on x86_64 architectures. For best compatibility you ABI compatibility on ARM64 architectures. For best compatibility you
should compile your application the same way. should compile your application the same way.
Please note that building SDL requires at least Xcode 4.6 and the 10.7 SDK Please note that building SDL requires at least Xcode 4.6 and the 10.7 SDK
(even if you target back to 10.5 systems). PowerPC support for Mac OS X has (even if you target back to 10.6 systems). PowerPC support for Mac OS X has
been officially dropped as of SDL 2.0.2. been officially dropped as of SDL 2.0.2. 32-bit Intel, using an older Xcode
release, is still supported at the time of this writing, but current Xcode
releases no longer support it, and eventually neither will SDL.
To use the library once it's built, you essential have two possibilities: To use the library once it's built, you essential have two possibilities:
use the traditional autoconf/automake/make method, or use Xcode. use the traditional autoconf/automake/make method, or use Xcode.
==============================================================================
Caveats for using SDL with Mac OS X
==============================================================================
Some things you have to be aware of when using SDL on Mac OS X: # Caveats for using SDL with Mac OS X
- If you register your own NSApplicationDelegate (using [NSApp setDelegate:]), If you register your own NSApplicationDelegate (using [NSApp setDelegate:]),
SDL will not register its own. This means that SDL will not terminate using SDL will not register its own. This means that SDL will not terminate using
SDL_Quit if it receives a termination request, it will terminate like a SDL_Quit if it receives a termination request, it will terminate like a
normal app, and it will not send a SDL_DROPFILE when you request to open a normal app, and it will not send a SDL_DROPFILE when you request to open a
file with the app. To solve these issues, put the following code in your file with the app. To solve these issues, put the following code in your
NSApplicationDelegate implementation: NSApplicationDelegate implementation:
- (NSApplicationTerminateReply)applicationShouldTerminate:(NSApplication *)sender ```objc
{ - (NSApplicationTerminateReply)applicationShouldTerminate:(NSApplication *)sender
{
if (SDL_GetEventState(SDL_QUIT) == SDL_ENABLE) { if (SDL_GetEventState(SDL_QUIT) == SDL_ENABLE) {
SDL_Event event; SDL_Event event;
event.type = SDL_QUIT; event.type = SDL_QUIT;
@ -62,10 +77,10 @@ Some things you have to be aware of when using SDL on Mac OS X:
} }
return NSTerminateCancel; return NSTerminateCancel;
} }
- (BOOL)application:(NSApplication *)theApplication openFile:(NSString *)filename - (BOOL)application:(NSApplication *)theApplication openFile:(NSString *)filename
{ {
if (SDL_GetEventState(SDL_DROPFILE) == SDL_ENABLE) { if (SDL_GetEventState(SDL_DROPFILE) == SDL_ENABLE) {
SDL_Event event; SDL_Event event;
event.type = SDL_DROPFILE; event.type = SDL_DROPFILE;
@ -74,33 +89,34 @@ Some things you have to be aware of when using SDL on Mac OS X:
} }
return NO; return NO;
} }
```
============================================================================== # Using the Simple DirectMedia Layer with a traditional Makefile
Using the Simple DirectMedia Layer with a traditional Makefile
==============================================================================
An existing autoconf/automake build system for your SDL app has good chances An existing autoconf/automake build system for your SDL app has good chances
to work almost unchanged on OS X. However, to produce a "real" Mac OS X binary to work almost unchanged on macOS. However, to produce a "real" Mac binary
that you can distribute to users, you need to put the generated binary into a that you can distribute to users, you need to put the generated binary into a
so called "bundle", which basically is a fancy folder with a name like so called "bundle", which is basically a fancy folder with a name like
"MyCoolGame.app". "MyCoolGame.app".
To get this build automatically, add something like the following rule to To get this build automatically, add something like the following rule to
your Makefile.am: your Makefile.am:
bundle_contents = APP_NAME.app/Contents ```make
APP_NAME_bundle: EXE_NAME bundle_contents = APP_NAME.app/Contents
APP_NAME_bundle: EXE_NAME
mkdir -p $(bundle_contents)/MacOS mkdir -p $(bundle_contents)/MacOS
mkdir -p $(bundle_contents)/Resources mkdir -p $(bundle_contents)/Resources
echo "APPL????" > $(bundle_contents)/PkgInfo echo "APPL????" > $(bundle_contents)/PkgInfo
$(INSTALL_PROGRAM) $< $(bundle_contents)/MacOS/ $(INSTALL_PROGRAM) $< $(bundle_contents)/MacOS/
```
You should replace EXE_NAME with the name of the executable. APP_NAME is what You should replace `EXE_NAME` with the name of the executable. `APP_NAME` is
will be visible to the user in the Finder. Usually it will be the same what will be visible to the user in the Finder. Usually it will be the same
as EXE_NAME but capitalized. E.g. if EXE_NAME is "testgame" then APP_NAME as `EXE_NAME` but capitalized. E.g. if `EXE_NAME` is "testgame" then `APP_NAME`
usually is "TestGame". You might also want to use `@PACKAGE@` to use the package usually is "TestGame". You might also want to use `@PACKAGE@` to use the
name as specified in your configure.ac file. package name as specified in your configure.ac file.
If your project builds more than one application, you will have to do a bit If your project builds more than one application, you will have to do a bit
more. For each of your target applications, you need a separate rule. more. For each of your target applications, you need a separate rule.
@ -108,10 +124,12 @@ more. For each of your target applications, you need a separate rule.
If you want the created bundles to be installed, you may want to add this If you want the created bundles to be installed, you may want to add this
rule to your Makefile.am: rule to your Makefile.am:
install-exec-hook: APP_NAME_bundle ```make
install-exec-hook: APP_NAME_bundle
rm -rf $(DESTDIR)$(prefix)/Applications/APP_NAME.app rm -rf $(DESTDIR)$(prefix)/Applications/APP_NAME.app
mkdir -p $(DESTDIR)$(prefix)/Applications/ mkdir -p $(DESTDIR)$(prefix)/Applications/
cp -r $< /$(DESTDIR)$(prefix)Applications/ cp -r $< /$(DESTDIR)$(prefix)Applications/
```
This rule takes the Bundle created by the rule from step 3 and installs them This rule takes the Bundle created by the rule from step 3 and installs them
into "$(DESTDIR)$(prefix)/Applications/". into "$(DESTDIR)$(prefix)/Applications/".
@ -119,27 +137,30 @@ into "$(DESTDIR)$(prefix)/Applications/".
Again, if you want to install multiple applications, you will have to augment Again, if you want to install multiple applications, you will have to augment
the make rule accordingly. the make rule accordingly.
But beware! That is only part of the story! With the above, you end up with But beware! That is only part of the story! With the above, you end up with
a bare bone .app bundle, which is double clickable from the Finder. But a barebones .app bundle, which is double-clickable from the Finder. But
there are some more things you should do before shipping your product... there are some more things you should do before shipping your product...
1) The bundle right now probably is dynamically linked against SDL. That 1. The bundle right now probably is dynamically linked against SDL. That
means that when you copy it to another computer, *it will not run*, means that when you copy it to another computer, *it will not run*,
unless you also install SDL on that other computer. A good solution unless you also install SDL on that other computer. A good solution
for this dilemma is to static link against SDL. On OS X, you can for this dilemma is to static link against SDL. On OS X, you can
achieve that by linking against the libraries listed by achieve that by linking against the libraries listed by
```bash
sdl-config --static-libs sdl-config --static-libs
```
instead of those listed by instead of those listed by
```bash
sdl-config --libs sdl-config --libs
```
Depending on how exactly SDL is integrated into your build systems, the Depending on how exactly SDL is integrated into your build systems, the
way to achieve that varies, so I won't describe it here in detail way to achieve that varies, so I won't describe it here in detail
2) Add an 'Info.plist' to your application. That is a special XML file which 2. Add an 'Info.plist' to your application. That is a special XML file which
contains some meta-information about your application (like some copyright contains some meta-information about your application (like some copyright
information, the version of your app, the name of an optional icon file, information, the version of your app, the name of an optional icon file,
and other things). Part of that information is displayed by the Finder and other things). Part of that information is displayed by the Finder
@ -148,30 +169,31 @@ there are some more things you should do before shipping your product...
As a final remark, let me add that I use some of the techniques (and some As a final remark, let me add that I use some of the techniques (and some
variations of them) in Exult and ScummVM; both are available in source on variations of them) in [Exult](https://github.com/exult/exult) and
[ScummVM](https://github.com/scummvm/scummvm); both are available in source on
the net, so feel free to take a peek at them for inspiration! the net, so feel free to take a peek at them for inspiration!
============================================================================== # Using the Simple DirectMedia Layer with Xcode
Using the Simple DirectMedia Layer with Xcode
==============================================================================
These instructions are for using Apple's Xcode IDE to build SDL applications. These instructions are for using Apple's Xcode IDE to build SDL applications.
- First steps ## First steps
The first thing to do is to unpack the Xcode.tar.gz archive in the 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). top level SDL directory (where the Xcode.tar.gz archive resides).
Because Stuffit Expander will unpack the archive into a subdirectory, Because Stuffit Expander will unpack the archive into a subdirectory,
you should unpack the archive manually from the command line: you should unpack the archive manually from the command line:
cd [path_to_SDL_source] ```bash
tar zxf Xcode.tar.gz cd [path_to_SDL_source]
tar zxf Xcode.tar.gz
```
This will create a new folder called Xcode, which you can browse This will create a new folder called Xcode, which you can browse
normally from the Finder. normally from the Finder.
- Building the Framework ## Building the Framework
The SDL Library is packaged as a framework bundle, an organized The SDL Library is packaged as a framework bundle, an organized
relocatable folder hierarchy of executable code, interface headers, relocatable folder hierarchy of executable code, interface headers,
@ -185,56 +207,75 @@ By default, the framework bundle "SDL.framework" is installed in
it to be located there. However, it will function the same in any of the it to be located there. However, it will function the same in any of the
following locations: following locations:
~/Library/Frameworks * ~/Library/Frameworks
/Local/Library/Frameworks * /Local/Library/Frameworks
/System/Library/Frameworks * /System/Library/Frameworks
- Build Options ## Build Options
There are two "Build Styles" (See the "Targets" tab) for SDL.
"Deployment" should be used if you aren't tweaking the SDL library.
"Development" should be used to debug SDL apps or the library itself.
- Building the Testers There are two "Build Styles" (See the "Targets" tab) for SDL.
Open the SDLTest project and build away! "Deployment" should be used if you aren't tweaking the SDL library.
"Development" should be used to debug SDL apps or the library itself.
- Using the Project Stationary ## Building the Testers
Copy the stationary to the indicated folders to access it from
the "New Project" and "Add target" menus. What could be easier?
- Setting up a new project by hand Open the SDLTest project and build away!
Some of you won't want to use the Stationary so I'll give some tips:
* Create a new "Cocoa Application"
* Add src/main/macosx/SDLMain.m , .h and .nib to your project
* Remove "main.c" from your project
* Remove "MainMenu.nib" from your project
* Add "$(HOME)/Library/Frameworks/SDL.framework/Headers" to include path
* Add "$(HOME)/Library/Frameworks" to the frameworks search path
* Add "-framework SDL -framework Foundation -framework AppKit" to "OTHER_LDFLAGS"
* Set the "Main Nib File" under "Application Settings" to "SDLMain.nib"
* Add your files
* Clean and build
- Building from command line ## Using the Project Stationary
Use pbxbuild in the same directory as your .pbproj file
- Running your app Copy the stationary to the indicated folders to access it from
You can send command line args to your app by either invoking it from the "New Project" and "Add target" menus. What could be easier?
the command line (in *.app/Contents/MacOS) or by entering them in the
"Executables" panel of the target settings.
- Implementation Notes ## Setting up a new project by hand
Some things that may be of interest about how it all works...
* Working directory Some of you won't want to use the Stationary so I'll give some tips:
As defined in the SDL_main.m file, the working directory of your SDL app
is by default set to its parent. You may wish to change this to better * Create a new "Cocoa Application"
suit your needs. * Remove "main.c" from your project
* You have a Cocoa App! * Remove "MainMenu.nib" from your project
Your SDL app is essentially a Cocoa application. When your app * Add "$(HOME)/Library/Frameworks/SDL.framework/Headers" to include path
starts up and the libraries finish loading, a Cocoa procedure is called, * Add "$(HOME)/Library/Frameworks" to the frameworks search path
which sets up the working directory and calls your main() method. * Add "-framework SDL -framework Foundation -framework AppKit" to "OTHER_LDFLAGS"
You are free to modify your Cocoa app with generally no consequence * Set the "Main Nib File" under "Application Settings" to "SDLMain.nib"
to SDL. You cannot, however, easily change the SDL window itself. * Add your files
Functionality may be added in the future to help this. * Clean and build
## Building from command line
Use `xcode-build` in the same directory as your .pbxproj file
## Running your app
You can send command line args to your app by either invoking it from
the command line (in *.app/Contents/MacOS) or by entering them in the
Executables" panel of the target settings.
# Implementation Notes
Some things that may be of interest about how it all works...
## Working directory
In SDL 1.2, the working directory of your SDL app is by default set to its
parent, but this is no longer the case in SDL 2.0. SDL2 does change the
working directory, which means it'll be whatever the command line prompt
that launched the program was using, or if launched by double-clicking in
the finger, it will be "/", the _root of the filesystem_. Plan accordingly!
You can use SDL_GetBasePath() to find where the program is running from and
chdir() there directly.
Known bugs are listed in the file "BUGS.txt". ## You have a Cocoa App!
Your SDL app is essentially a Cocoa application. When your app
starts up and the libraries finish loading, a Cocoa procedure is called,
which sets up the working directory and calls your main() method.
You are free to modify your Cocoa app with generally no consequence
to SDL. You cannot, however, easily change the SDL window itself.
Functionality may be added in the future to help this.
# Bug reports
Bugs are tracked at [the GitHub issue tracker](https://github.com/libsdl-org/SDL/issues/).
Please feel free to report bugs there!