I’m including the Juce sources with the amalgamated cpp files as well as the amalgamated header (projects created with Introjucer).
When an assertion fails inside Juce code the debugger breaks but won’t jump to the assertion’s line. This is quite annoying since I also can’t access the source code directly in XCode as they are included in the amalgamated cpp files. So what I do atm is look in the debugging console in which file the assertion failed, search it with Finder, open it and scroll to the mentioned line.
I assume this isn’t the usual way to handle this.
Is there any way to get XCode to behave as one would expect it (jump to the line that broke the debugger)?
I haven’t felt the need to debug with breakpoints inside the Juce code on Mac but I assume similar problems arise when doing so.