This happens because the generated header uses @import (appropriately guarded) rather than #import. Copying some notes out of Radar:

• For framework modules with umbrella headers, we can just include the umbrella header.

• For header modules with umbrella headers, we can include the umbrella header by absolute (sysroot-relative) path.

• For modules without umbrella headers, we can include every header in the appropriate submodule manually.

That last may not actually work because some submodule headers depend on other headers having been included.

(I'm not actually sure the "sysroot-relative" thing works, but even just handling the simple "frameworks with umbrella header" case would be a good improvement that probably follows the 80/20 rule.)

I got a start on this (imports.patch), but ran into difficulty figuring out how to actually spell the headers. The attached patch is doing some terrible parent directory sniffing to see if we're in a framework or something that looks like a search path, but I don't know if that's really the way to go.

Comment by Matthew Benedict (JIRA)

I have this issue in another configuration. I have a drawer controller with open access level declared in a package, which I have imported and inherited from in a Swift file. Upon compiling, the same error occurs: "Cannot find interface declaration for 'ZKDrawerController', superclass of 'ReviewContainerViewController'"

@belkadan, or anyone else, should I post this as a separate issue, or is this the same? Thank you!

Where is that error emitted? Is it from an Objective-C++ source file? If not, it's probably a different issue.

Comment by Matthew Benedict (JIRA)

@belkadan, I reported it at https://bugs.swift.org/browse/SR-12954 as a separate issue based on your comment, before realising that they are in fact one and the same issue. Could you please mark that as a duplicate of this? Hopefully the additional information helps you resolve this!

You should be able to do it too: go to your new bug and choose Resolve Issue, then select "Duplicate" and add this SR as the issue it duplicates.