> On Nov 2, 2016, at 09:31, Ken Cunningham <ken.cunningham.web...@gmail.com> 
> wrote:
> On 2016-11-02, at 2:03 AM, Jeremy Huddleston Sequoia wrote:
>> Do you know *why* it is requiring the 10.7 SDK to build?  Why can't libsdl2 
>> use the 10.6 SDK effectively?
> I took a quick look at the code. It has a lot of AVAILABILITY_ macros in it, 
> a few mentioning 10.7, most of them mentioning IOS / IPHONE things.

I don't see any AVAILABILITY_ macros.  I do see on interesting reference to 
10.7 in src/video/cocoa/SDL_cocoawindow.m:

~/src/macports/dports/devel/libsdl2/work/SDL2-2.0.5 $ ack AVAILABILITY_

~/src/macports/dports/devel/libsdl2/work/SDL2-2.0.5 $ ack 10\\.7
19:32-bit and 64-bit Intel architectures), on Mac OS X 10.7 and newer, by using
32:Please note that building SDL requires at least Xcode 4.6 and the 10.7 SDK

576: *   the OS isn't at least Mac OS X Lion (10.7). This hint must be set 

47:     *  It happens to work, as of 10.7, but we're going to see if

178:    /* specify a profile if we're on Lion (10.7) or later. */
331:     * supported on 10.7+. */

155:    /* The IOPM assertion API can disable the screensaver as of 10.7. */

26:# error SDL for Mac OS X must be built with a 10.7 SDK or above.


That's just:

# error SDL for Mac OS X must be built with a 10.7 SDK or above.
#endif /* MAC_OS_X_VERSION_MAX_ALLOWED < 1070 */

which doesn't indicate what the actual problem is.  What happens if you remove 

> I assume that some of those macros don't work right with the 10.6 SDK, but 
> the details of exactly which ones I didn't look into.
> It seems like a lot of work (too much!) to try to fix that code, and the next 
> version of libsdl2 would just break it all anyway.
> The 10.7 SDK shouldn't be hard to find for anyone motivated to do so, and 
> once it's on the buildbot (and we get that libc++ buildbot naming issue 
> organized) that would make it sorta moot, I would think?
> Thanks,
> Ken

Attachment: smime.p7s
Description: S/MIME cryptographic signature

macports-users mailing list

Reply via email to