Re: Where are the OpenAL dynamic or static libraries on MacOS 10.5.7 with with XCode 312?

On 11/27/09, "Alexander Günzel" <[email protected]> wrote:
> Hello especially to E. Wing,
>
> who gave a wonderful answer to Luca Brayda in the thread "[Openal]
> cannot find openal 1.1 for MacOSX" in November 2009. This helped me
> to find the openal include files. But at the same location I can't
> find the dynamic or static OpenAl libraries, which I need for let my
> linker do it's work. It always complains about unresolved symbols
> from OpenAL functions.
>
> So my question is:
> In which path do I find the dynamic or static OpenAl libraries under
> MacOS X 10.5.7 with XCode 312?
>

A .framework on OS X is a self-contained bundle that contains both
header files and dynamic libraries (and sometimes extra resources) all
in a single package. You want to link against that same
OpenAL.framework I referred to in the previous email.

In Xcode, the most common convention is to Ctrl-click on "External
Frameworks and Libraries" in the Groups & Files panel to bring up a
contextual menu and do Add->Existing Frameworks.

Then look for the OpenAL.framework. Hopefully you'll only see one
entry. If you see multiple, it probably means you installed a 3rd
party version somewhere which might mess you up. You'll need to guess
which is the correct one. Lastly, you need to add it to the correct
target in your Xcode project if you have multiple build targets. To
verify, select your desired target as the active build target, click
on the
"External Frameworks and Libraries" to highlight the group and in the
main-right-side view, select the "Details" tab, and look for the
OpenAL.framework and make sure the checkbox is checked.


> I also installed the package "OpenAL_Installer_OSX.dmg", but it ended
> silently and so I don't know, what it did.

Hopefully it didn't do anything. You shouldn't be installing anything
like this. Where did you get this? Through the years, I've been
getting odd questions about linking problems with OpenAL on OS X and
its always the case that somebody installed a 3rd party OpenAL which
was built wrong or really old that they were linking to instead of the
system supplied one. Everyone claims they never installed it even
though its sitting right there on their system, but it had to come
from somewhere, and I've been wanting to know where its been coming
from.

Make sure you don't have an OpenAL.framework in /Library/Frameworks or
~/Library/Frameworks.

-Eric

_______________________________________________
Openal mailing list
[email protected]
http://opensource.creative.com/mailman/listinfo/openal