When I create two or more plug-ins using the auwrapper, I get warnings like this when running auval -a:

objc[47636]: Class SMTGCocoa_NSViewWrapperForAU is implemented in both /Library/Audio/Plug-Ins/Components/MyPlugin2_AU.component/Co ntents/MacOS/MyPlugin2_AU and /Library/Audio/Plug-Ins/Components/MyPlugin1_AU.component/Co ntents/MacOS/MyPlugin1_AU. One of the two will be used. Which one is undefined.
objc[47636]: Class SMTGCocoa_AUViewFactory_Version_1 is implemented in both /Library/Audio/Plug-Ins/Components/MyPlugin2_AU.component/Co ntents/MacOS/MyPlugin2_AU and /Library/Audio/Plug-Ins/Components/MyPlugin1_AU.component/Co ntents/MacOS/MyPlugin1_AU. One of the two will be used. Which one is undefined.

I'm not all that familiar with how Cocoa works in this regard, but shouldn't the plug-in project be doing something during the compile to make sure those names are unique? When used in this manner, they're part of auwrapper.a, a library that is used by multiple plug-in projects, and so the names exist in multiple plug-ins. How can I resolve this name clash?

Thanks,
Howard

I found one way to resolve this... I copied the entire auwrapper project into my own project folder for each project, and made a different library for each, with different names for those two Objective-C classes. So now each of my plug-ins has distinct names.

There's most likely a better (certainly less hack-y) way to do this, but this was fast and easy and works.