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 1373 - Build fails on MacOSX, iOS
Summary: Build fails on MacOSX, iOS
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: build (show other bugs)
Version: 2.0.0
Hardware: x86 Mac OS X 10.6
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-16 01:57 UTC by Jack Jansen
Modified: 2012-01-17 06:05 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Jansen 2012-01-16 01:57:24 UTC 
As of recently, builds are starting to fail for SDL 1.3.0-6217, for MacOSX (both 10.6 and 10.7). This is configure/make builds (not sure whether you're also doing xcode-based builds for MacOSX, but if you are we are not using them).

The problem seems to be that SDL_video.c references X11_bootstrap() which doesn't exist.

I've tried configuring with --disable-video-x11 and even with --without-video, but this doesn't seem to help, probably because when building for the mac SDL uses SDL_config_macosx.h always (ignoring the SDL_config_generated.h which was created by configure.
Comment 1 Sam Lantinga 2012-01-16 16:25:01 UTC 
I switched all the Mac builds to use SDL_config_macosx.h, so that any SDL library that's built is binary compatible with others.

Is the problem that you don't have the X11 includes and libraries on your system?
Comment 2 Jack Jansen 2012-01-17 03:35:52 UTC 
Indeed, I don't have the X11 libraries installed. This is on purpose, because for binary distribution of the resulting project (Ambulant, www.ambulantplayer.org) we don't want to have dependencies on external packages (or optional Apple packages).

I can see your point with binary compatibility (even though it is at odds with my use case:-). Would it be possible to weak-link against the X11 libraries or something like that, so that even though I install the X11 stuff on my system there is no requirement for end users to do so too?
Comment 3 Sam Lantinga 2012-01-17 05:05:48 UTC 
We do indeed dynamically load the X11 libraries at runtime so there is no requirement for those libraries to be present on the end user's system.
Comment 4 Jack Jansen 2012-01-17 05:37:22 UTC 
I have now reverted the configure options (for MacOSX) to what they were two weeks ago, and everything seems to build fine again. Probably an operator error.

Sorry for wasting your time,