gitea/SDL3_fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use Apple's nomenclature for macOS and iOS

Browse Source 
Fixes https://github.com/libsdl-org/SDL/issues/6621
This commit is contained in:
Sam Lantinga
2022-11-25 16:00:06 -08:00
parent 5fb3eb9475
commit cc1f9eb983
83 changed files with 291 additions and 296 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/README-macos.md
View File

@@ -1,7 +1,6 @@
# Mac OS X (aka macOS).
# macOS
These instructions are for people using Apple's Mac OS X (pronounced
"ten"), which in newer versions is just referred to as "macOS".
These instructions are for people using Apple's macOS.
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
@@ -21,8 +20,7 @@ sudo cmake --install .
You can also build SDL as a Universal library (a single binary for both
64-bit Intel and ARM architectures), by using the build-scripts/clang-fat.sh
script.
64-bit Intel and ARM architectures):
```bash
mkdir build
@@ -32,10 +30,6 @@ cmake --build .
sudo cmake --install .
```
This script builds SDL with 10.9 ABI compatibility on 64-bit Intel and 11.0
ABI compatibility on ARM64 architectures. For best compatibility you
should compile your application the same way.
Please note that building SDL requires at least Xcode 6 and the 10.9 SDK.
PowerPC support for macOS has been officially dropped as of SDL 2.0.2.
32-bit Intel and macOS 10.8 runtime support has been officially dropped as
@@ -45,7 +39,7 @@ To use the library once it's built, you essential have two possibilities:
use the traditional autoconf/automake/make method, or use Xcode.
# Caveats for using SDL with Mac OS X
# Caveats for using SDL with macOS
If you register your own NSApplicationDelegate (using [NSApp setDelegate:]),
SDL will not register its own. This means that SDL will not terminate using
@@ -133,17 +127,17 @@ there are some more things you should do before shipping your product...
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*,
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 macOS, you can
achieve that by linking against the libraries listed by
```bash
sdl-config --static-libs
sdl3-config --static-libs
```
instead of those listed by
```bash
sdl-config --libs
sdl3-config --libs
```
Depending on how exactly SDL is integrated into your build systems, the