Sounds like a Jordan thing.

That really sounds like the module map is wrong.

…or rather, we should build a dylib rather than a framework for C targets in the Xcode generator, or maybe the package manager should provide the "link" command in the module map rather than the user.

Both the compiler and Xcode are behaving as expected.

SwiftPM generates correct modulemap for swift-build (dylibs) and Xcode (framework) project if the C library layout is supported.
If user provides a modulemap swiftpm doesn't try to generate a modulemap.

I'll suggest let swiftpm generate modulemap for you so it works with both Xcode and swift-build. All you have to do is move the public headers to include directory (and ofc remove the current modulemap).

btw, the rules are here: https://github.com/apple/swift-package-manager/blob/master/Sources/PackageLoading/ModuleMapGenerator.swift#L45

Comment by Ian Partridge (JIRA)

Thank you @aciidb0mb3r! With this hint we were able to fix the issue on Kitura's side. 👍

Sounds like we'll still want some way to allow custom module maps with Xcode support, but it's no longer urgent.

@ddunbar @abertelrud
I am not sure about the correct solution.
We can:

1. switch back to dylibs
2. have a --dylib mode when generating Xcode project
3. allow specifying a custom module map for Xcode

I am not sure either. We don't officially support Swift dylibs in Xcode, which makes me question whether we should use them. On the other hand, it isn't clear our model is strong enough to actually support this... in particular with regard to RPATH-type things, which currently there is no way to specify.

Fixed in #630