I can’t find a thread that expresses this point explicitly, so I’m posting the point here.
I’ve already read these threads, that - while useful - have not got me a workaround as yet:
I have two main dev macs, my 10.6 MacPro at home and my 10.7 MacPro in the office. When I’m at home (10.6) - irrespective of whether I’m using XCode 3 or 4.1 preview - I can make a few adjustments to the project file created by the Introducer and I’m on my way. *Tick!
However, the same project (either fresh or imported) creates a slew of new errors when I bring it to the office (10.7).
Aside from AUDebugDispatcher being notably absent from the current CoreAudio SDK (easily removing from the list of file refs), LLVM will flag errors routed in these headers:
Unknown type: AudioComponentPlugInInterface
Unknown type: AudioComponentMethod
All of which are referenced by the Juce AU wrapper “group”, either from /Developer/Extras/CoreAudio or XCode.app/Contents/Developer/Extras/CoreAudio (as of v4.3, assuming you’ve followed Jule’s instructions).
The errors themselves are mundane, but prevent Juce plug-in framework from working in the way that it was intended, i.e. out of the box.
I should also mention that the Base SDK is correctly, i.e. 10.6, and the header include paths are:
If I set this flag:
#define JucePlugin_Build_AU 0
…and remove the Apple AU Files group from the project, I can build the VST2.4 part no problem at all.
I know Jules is probably busy with other matters, but I do think this is a big enough problem to need at least an all-in-one-place howto doc to get Juce AU Wrapper reconciled with CoreAudio. The Introducer can be fixed later. If this turns out to be Apple’s screw-up then this needs to be established with due dilligence and the appropriate people nagged. I have some contact info for that.
All the best,