[SDL] SDL 1.2 build still broken on Macos X 10.9 one year later.
douglas.linder at gmail.com
Thu Sep 11 18:30:01 PDT 2014
> I'm not sure why can't the dynamic library just be included inside the
You have to setup the @rpath correctly using install_name_tool for that to
work (which is trivial, but not obvious; it breaks 'cross platform
Using a statically linked sdl library is easier I suppose...
> The BEST solution is to have SDL's standard distribution on OS X be as a
I'd strongly recommend shipping the sdl dylib and all it's child
dependencies as part of the application bundle; particular the SDL_foo*
libraries with all their dependencies. Application bundles are specifically
designed to allow this to work.
I know that's somewhat counter to the 'use system libraries' approach, but
on most unix systems installing an application doesn't cause the
application to try to write it's own copies of libraries into /lib/ :P
Lots of things try to install SDL as a framework as part of their
installation; and extremely irritatingly they will consistently break each
other in my experience.
On Thu, Sep 11, 2014 at 12:22 PM, Sik the hedgehog <
sik.the.hedgehog at gmail.com> wrote:
> 2014-09-10 19:31 GMT-03:00, Ryan C. Gordon <icculus at icculus.org>:
> >> Another is that the README says to static link against SDL
> > Huh, that's terrible advice for LGPL'd code.
> Pretty sure that advice was meant for SDL2 (which is under a more
> permissive license). Even then, I'm not sure why can't the dynamic
> library just be included inside the bundle? (but I never made anything
> for OSX so I don't know if that'd work)
> SDL mailing list
> SDL at lists.libsdl.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SDL