RE: Cocoa IN Audiounit
RE: Cocoa IN Audiounit
- Subject: RE: Cocoa IN Audiounit
- From: "Jeremy Jurksztowicz" <email@hidden>
- Date: Fri, 13 May 2005 17:01:44 +0000
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?
Thanks for all the feedback,
Jeremy Jurksztowicz
_______________________________________________
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