Re: Emagic porting SDK
Re: Emagic porting SDK
- Subject: Re: Emagic porting SDK
- From: Marc Poirier <email@hidden>
- Date: Fri, 12 Sep 2003 08:16:13 -0500 (CDT)
On Fri, 12 Sep 2003, Peter from LinPlug wrote:
>
Now it all compiles + links fine, however, its not
>
detected as AU instrument by Logic or other AU hosts.
>
>
There is a bundle created, which when I examine the contents looks fine,
>
the Info.plist was of type Codewarrior-Source, but I could open it with
>
Property List Editor, it was looking fine and resaving lets it be a type
>
XML property list file.
A few ideas:
It might be a Component Manager discovery thing. Try moving your
.component bundle out of and then back into the Components directory.
More info:
http://www.mat.ucsb.edu:8000/CoreAudio/79
Did you make a .r file for the Component resource stuff?
Do you have your extry points defined or settings set up in some way that
they are being exported properly (not knowing what compiler you're using,
it's hard to be more specific)? You can try running:
nm -g <your-bundle-executable>
replacing <your-bundle-executable> with the full path to the exectubable
in your bundle (blah.component/Contents/MacOS/blah like that). Look for
items marked with T before them and look for the names of your entry
points.
Along those same lines, did you use the COMPONENT_ENTRY macro for each
component's entry point?
I hope that helps,
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.