Mac Sdl Library Not Found

Contents

Mar 10, 2014 How To Fix 'No Library Found' KONTAKT OfficiallyShubh. Unsubscribe from OfficiallyShubh? Cancel Unsubscribe. Subscribe Subscribed Unsubscribe 5.18K. Install SDL 2 on Mac OS X. 2) Next open the dmg and copy the SDL2.framework to /Library/Frameworks. To go directly to a path in finder, press command+shift+g. Simple DirectMedia Layer is a cross-platform development library designed to provide low level access to audio, keyboard, mouse, joystick, and graphics hardware via OpenGL and Direct3D. It is used by video playback software, emulators, and popular games including Valve 's award winning catalog and many Humble Bundle games. It works fine until I tried it on one of the mac 10.9 machine. The library uses sdl framework. No suitable image found. Did find: /Library/Frameworks/SDL. Found a solution. I'll leave this here for future googlers. I installed the monogame 3.7 build from the Development Builds section of http://www.monogame.net.

FAQ: Mac OS X

What is supported?

Sdl Library Download

SDL 2.0.0 supports Mac OS X 10.5 and newer, using either Xcode or the classic Unix-style build system. Currently only Xcode can be used to build the SDL Framework. The Unix-style build system creates classic shared and static versions of the SDL library.

Jul 22, 2011 Fortunately, this is easy to reverse and if you wish you can switch the behavior and instead show Library all the time with a quick terminal command. This tutorial will detail four different ways to access the User Library folder in Mac OS X from Mt Lion and beyond. Navigate to library on mac. Jan 12, 2020 You can access the hidden Library folder without using Terminal, which has the side effect of revealing every hidden file on your Mac. This method will only make the Library folder visible, and only for as long as you keep the Finder window for the Library folder open.

For the latest information see the page about Installation.

What is the difference between the Xcode and the Unix-style build system?

The SDL-devel package contains the SDL libraries in the form of a Framework. That is perfectly fine as long as you want to develop using Xcode. However, applications which use a configure script almost always require SDL to be installed Unix-style.

When installed as a Framework, all SDL files (the library and the header files) are aggregated into a .framework bundle, and installed together into /Library/Frameworks/ or ~/Library/Frameworks/. There, Xcode can find it. But packages which want to use SDL but employ a Unix-style build system are usually not able to find SDL there (there are a few exceptions where people hand modified their configure scripts to allow using Frameworks on OS X, but those are rare).

When installing Unix-style, SDL gets installed into /usr/local/bin, /usr/local/include and /usr/local/lib (the exact path can vary, for example the Fink SDL package will use /sw instead of /usr/local by default). This way, build system tuned to support generic Unix systems are able to find them.

How do I install SDL Unix-style?

Either you can compile and install it from source (via the usual ./configure && make && make install procedure). Or install it via some kind of packaging system which ships premade packages for SDL. For example, both Fink and MacPorts include packages which are suitable. You can learn more about them on their respective sites.

Note that as long as you static link the release builds of your application, it doesn't really matter which way you installed SDL -- for example, even if you installed it via Fink, if you static link SDL, your users do not have to install Fink.

How do I build an OpenGL application?

On Mac OS X, you access the OpenGL headers like so:

The header file 'SDL_opengl.h' includes these headers on all supported SDL systems.

If you are using Xcode, add OpenGL.framework to your project. On the command line, add:

-framework OpenGL

to the GCC or LD arguments in your Makefile

How do I include the SDL framework in my application?

Mac Sdl Library Not Found In California

One good strategy can be found here: Properly bundling .frameworks in your application package