Ah great, didn’t see that fix, thanks.\
By multiple plugs, I mean for example, a Delay plugin and a Filter plugin from the same project (each in multiple formats - VST, VST3, AU - of course).
I currently use multiple targets in the same project to do this.
Since the new example code already uses targets for plugin type separation, this become difficult.
Would it be easy to move the pluginprocessor code to the individual targets instead of having it in the shared code target? Then it would be easy to have multiple plugins in one project, since the “shared code” portion would include all the juce and user code, but not the plugin specific code.
Not sure if that’s possible though, since the framework would have to be happy without any entrance function. Juce_core also needs an entrance point I think?
Anyway, no biggie, I may eventually build out individual projects for each plugin … though it would mean that any time I change a setting or add a file, I need to do it many times instead of once. hmmm …