Trying to figure out where my plugin is burning CPU with XCode and Instruments I ran into an issue with the XCode configurations created in Projucer. For profiling I would need a config that is identical to “Release”, but has debug symbols enabled so I can see what’s happening in instruments. So I checked “Debugging enabled” on the Projucer config page. Only much later I realized, that this of course enabled all the debug code and that I was seeing bottlenecks where there are jassert() calls in the code.
Is there a way to make a config that creates debug symbols but does not define DEBUG _DEBUG and JUCE_DEBUG (1) ? Right now I have to manually edit the XCode config after each Projucer change which is of course error-prone should I profile again (and forget about it).