| Summary: | Build fails on MacOSX, iOS | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Jack Jansen <Jack.Jansen> |
| Component: | build | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED INVALID | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.0.0 | ||
| Hardware: | x86 | ||
| OS: | Mac OS X 10.6 | ||
|
Description
Jack Jansen
2012-01-16 01:57:24 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? 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? 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. 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, |