IS_STANDALONE / IS_DEV etc... strategy
baconpaul opened this issue · comments
Juce 6 provides a standalone essentially as a 'plugin type' and you don't really need spilt code. The Monique codebase has, I think from juce 4 days, a set of flags for is standalone or is plugin or is dev
When I finished #1 I ended up choosing the 'is plugin' version and building a standalone with that along with the VST3 and AU.
So I would love to understand what differences these flags cause and perhaps we could remove them and have a non-ifdef-segregated codebase in the core over time. This is the placeholder issue for that discussion.