libao issueshttps://gitlab.xiph.org/xiph/libao/-/issues2020-06-14T10:13:32Zhttps://gitlab.xiph.org/xiph/libao/-/issues/1834plugin directory cannot be relocated (OS X)2020-06-14T10:13:32ZHans Oesterholtplugin directory cannot be relocated (OS X)I'm using flac123, which in turn uses libao for it's audio output. I'm creating an application to play music on Mac OS X. I compiled Gtk, mpg123, flac123 and libao in a development environment and next I need to install flac123/libao as ...I'm using flac123, which in turn uses libao for it's audio output. I'm creating an application to play music on Mac OS X. I compiled Gtk, mpg123, flac123 and libao in a development environment and next I need to install flac123/libao as part of CuePlay in the /Applications/CuePlay.app directory.
This means that /<home>/workspace/cueplay/lib/ao/plugin-4 is relocated to /Applications/CuePlay.app/lib/ao/plugin-4.
The consequence is that plugins do not load anymore.
I think this is a bug. On Mac OS X, one should be able to install a library with the application and not on a fixed location.
For me this is a blocker, because I can't distribute my (open source) application this way.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/2210Warning: Carbon Component Manager is being depricated2020-06-14T10:09:15ZSethWarning: Carbon Component Manager is being depricatedApplications running in OS X 10.11 (El Capitan) have errors stating that Carbon Component Manager is deprecated:
This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support...Applications running in OS X 10.11 (El Capitan) have errors stating that Carbon Component Manager is deprecated:
This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.Monty MontgomeryMonty Montgomery