Re: Cocoa IN Audiounit
Re: Cocoa IN Audiounit
- Subject: Re: Cocoa IN Audiounit
- From: Doug Wyatt <email@hidden>
- Date: Fri, 13 May 2005 10:31:56 -0700
On May 13, 2005, at 10:01, Jeremy Jurksztowicz wrote:
Hello,
So basically I have come to the following conclusion, please point
out any holes :)
My audio unit is being loaded, it then loads some cocoa classes.
Then when my cocoa bundle is loaded it also loads some cocoa
classes. Some of these classes are by necessity the same as classes
in my audiounit, so the audiounit and view can share data by these
classes. So, my solution is to put the classes shared between the
audiounit and the cocoa view bundle into a dylib. Now the audiounit
loads the dylib at OpenAComponent(...), and when the cocoa view
bundle is loaded, it locates the already loaded dylib and does not
reload the cocoa classes... right? So a couple of questions, is a
dylib good, or a framework perhaps is better?
More importantly, where do I store the dylib so that the audiounit,
and the cocoa view can link to it, while keeping them all together?
I guess somwhere in the audiounit.component but where, and do I
need special linker flags (probably) to help my products link right?
A dylib inside your component bundle is fine, can't think of
advantages to a framework offhand.
I'll have to do some digging to find docs on where to put it and what
to tell the linker... I think it probably belongs in the MacOS
directory of the bundle. There are ways to tell Xcode to build and
load the dylib from bundle-relative locations. Maybe someone here
will know off the top of their heads and post before I can look it up.
Doug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden