I just tried to (and could indeed) reproduce this with one of the standard JUCE example projects (AudioAppDemo):
- opened the example project in the Projucer
- for the Xcode exporters (Debug and Release), added this to the “Custom Xcode flags”:
DEBUG_INFORMATION_FORMAT=dwarf-with-dsym, GCC_GENERATE_DEBUGGING_SYMBOLS=YES, DEPLOYMENT_POSTPROCESSING=YES - saved the project, opened it in Xcode and made sure that “Build Active Architecture Only” is also set to “No” for the Debug configuration
- built the 2 configurations in Xcode (just “Product → Build” for the Debug build, and “Product → Build for → Profiling” for the Release build)
Result:
- Debug builds fine without warnings
- Release builds fine too, but has 1567 warnings saying:
could not find referenced DIE
(in the step:Generate AudioAppDemo.app.dSYM)
I then also tried only building the x86_64 architecture, thinking it might have something to do with the new additional ARM configuration, by doing this in the Projucer:
- set “Valid Architectures” to only “x86_64” in the main Xcode exporter item
- set “macOS Architecture” to “Standard 64-bit” (for both the Debug and Release configurations)
Result:
Exactly the same: no warnings for Debug, lots of warnings for Release.
This was done with Xcode 12.4 and JUCE 6.0.8 (master branch on 6 April 2021, 90e8da0cfb54ac593cdbed74c3d0c9b09bad3a9f).
I’ll see if it’s still the same on the very latest / current master branch.
Edit: yes, exactly the same with the latest / current master branch (after rebuilding the Projucer and re-saving the example project of course).
At this point, I think I’ll just have to ignore this, unless @ed95, @t0m or someone else has any ideas?