I was wondering about that myself. I have header files that are internal to the framework so shouldn’t be public.
From: <cocoa@apple-dev.groups.io> on behalf of "Graham Cox via groups.io" <graham@...> Reply-To: "cocoa@apple-dev.groups.io" <cocoa@apple-dev.groups.io> Date: Wednesday, October 28, 2020 at 8:02 PM To: "cocoa@apple-dev.groups.io" <cocoa@apple-dev.groups.io> Subject: [cocoa-dev] Many new warnings after Xcode upgrade
EXTERNAL
I just updated to XCode 12.1, and my project is throwing a lot of new warnings about “double-quoted include in framework header”. This appears to be because of the build setting “Quoted include in Framework Header”, which is now a recommended
setting.
I can turn that off again, but what is this treally trying to tell me? These warnings appear to be bogus, in that yes, I’m building several frameworks as part of my workspace, but surely the files within those framework sources should be
simple double quotes, not refer to the framework headers - after all, it’s the framework I’m building!
I’m confused, but perhaps it’s because my project structure is incorrect. But I don’t want to go and change a whole bunch of stuff before I properly understand what should be done here.
Example errors in the output — note, this framework is one I just use “as is”, I’m not even building it (Sparkle).
