Re: Subject: MusicDevice/HandleNoteOne/Render
Re: Subject: MusicDevice/HandleNoteOne/Render
- Subject: Re: Subject: MusicDevice/HandleNoteOne/Render
- From: Marc Poirier <email@hidden>
- Date: Tue, 28 Jun 2005 19:31:07 -0400 (EDT)
I've debugged with Xcode without needing the AU to be in the build
directory (although perhaps there are some bugs with it that I just
haven't encountered). Also, I just make Xcode place the built AU into the
right place and don't use symlinks. Just make the following settings:
Installation Directory:
$(HOME)/Library/Audio/Plug-Ins/Components
Deployment Location:
yes
Installation Build Products Location:
/
(Note that, if you don't set that last bit, then everything will get put
into this weird-ass subdirectoy of /tmp or something like that, I forget
now, but it's a weird behavior that's been there since Project Builder
that Apple doesn't seem to think is a problem even though it confuses lots
of people and rarely gives anyone the default behavior that they want.)
Marc
On Tue, 28 Jun 2005, Bill Preder wrote:
(I was about to send this as Bill's response just came through. Figured I'd
throw it out there anyway:)
I could be wrong, but I suspect Xcode expects to find your plug-in in the
Development folder. This seems to be a wrinkle introduced with Xcode
2.x/Tiger. The work-around I've come up with is to make a symlink to the
Components folder named "Development" placed inside the Components folder.
i.e., assuming you want to debug a plug-in installed into
/Library/Audio/Plug-Ins/Components, do the following:
- Move or rename your existing Development folder
- fire up Terminal and type the following (note the omission of trailing
slashes):
ln -s /Library/Audio/Plug-Ins/Components /Library/Audio/Plug-
Ins/Components/Development
This will force Xcode to build directly to /Library/Audio/Plug-Ins/
Components, and you should be able to debug.
I've done the same with a "Deployment" symlink. I do wish this work-around
wasn't necessary, but it does the job.
- Bill
(addendum: I've had troubles off and on with making symlinks directly to my
AU itself in the past, but that certainly could have been due to pilot error
:-)
--- Daan Hermans <email@hidden> wrote:
At that time AULab is launched, I creat a new Audio Unit Instrument
track (Edit -> Add Audio Unit Instrument...), select my plug in it
and nothing happens. I would suspect that the Initialize(void)
function would be called by this time, awaking my breakpoint in the
debugger, but nothing happens there. If I hit the 'pause' button in
the debugger, I get all kinds of lower level looking code, without
any thing that I can trace back to my own code (hey that's what
compilers are for), not even to AUBase class kind of things.
_______________________________________________
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