Since JUCE switched from the polymorphic plugin build (same file functions as AU/VST/VST3/AAX/RTAS) to building separate targets for different formats, plugin installer sizes increased by a factor of about 4.
I understand that reverting to the polymorphic build is not a good option (because separate targets are needed for stand-alone, which is not a library, and AUv3).
So I suggest a different scheme that will yield the space savings of the polymorphic build, not only in the installers but also on the customer’s hard drives -
Build a library for the shared code, for which the only entry point / exposed symbol is
createPluginFilter, which will to be installed in some common folder (i.e
Application Support/), where the different targets for the plugin formats depend on that library for the symbol providing them with the actual
Do folks think that this is a good idea?
If so, should this be an option in the Projucer, or should it be the way to do things?
I’m willing to implement this scheme, and contribute it to JUCE if ROLI’s willing to accept it. In any case if I’ll implement it, it will be available in our branch (which anyone which can use JUCE can use freely)