We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2059 - #error SDL for Mac OS X only supports deploying on 10.5 and above.
Summary: #error SDL for Mac OS X only supports deploying on 10.5 and above.
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: 2.0.0
Hardware: x86 Mac OS X 10.6
: P2 normal
Assignee: Alex Szpakowski
QA Contact: Sam Lantinga
URL: https://github.com/Warzone2100/warzon...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-24 00:24 UTC by dak180
Modified: 2017-08-15 06:55 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dak180 2013-08-24 00:24:24 UTC
This happened when building wz2100 using the binary SDL framework on a 10.6 system using xcode 3.2.6 with the following settings:

ARCHS = x86_64
SDKROOT = macosx  // This maps to the newest sdk available, in my case 10.6
GCC_VERSION = com.apple.compilers.llvm.clang.1_0  // This is c++ so it will actually be llvm-gcc
MACOSX_DEPLOYMENT_TARGET = 10.6

it persisted even when adding the following:

GCC_PREPROCESSOR_DEFINITIONS = OS_X_VERSION_MIN_REQUIRED=1060
Comment 1 (disabled) Jørgen Tjernø 2014-01-07 02:38:25 UTC
dak180, is this still happening, with the latest SDL2 from hg? What is the specific line run by Xcode to build the file that's causing the problem? The MACOSX_DEPLOYMENT_TARGET should be fine left at 10.5 The GCC_PREPROCESSOR_DEFINITION should definitely not be needed.
Comment 2 (disabled) Jørgen Tjernø 2014-01-07 02:39:04 UTC
(Also, just the command line run by Xcode with the binary framework is fine, without top-of-tree SDL.)
Comment 3 Sam Lantinga 2017-08-15 06:55:30 UTC
I believe this is fixed in the latest SDL snapshot:
http://www.libsdl.org/tmp/SDL-2.0.zip

Please reopen the bug if you're still having issues.

Thanks!