@swift-ci create

I am getting this error with both 5.1.3 and ToT swift-5.2-branch:

<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "/Users/ankit/tmp/SwiftPMProtobuf/Protobuf/source/src/google/protobuf/source_context.pb.h"
        ^
/Users/ankit/tmp/SwiftPMProtobuf/Protobuf/source/src/google/protobuf/source_context.pb.h:7:10: error: 'limits' file not found
#include <limits>
         ^
/Users/ankit/tmp/foo/Sources/foo/main.swift:1:8: error: could not build Objective-C module 'Protobuf'
import Protobuf
       ^

Hmmm. limits.h is a standard C++ header that I am finding in my different runtime /usr/include directories. Maybe it is being found through stuff I have installed via brew.

I will find a clean machine to get it building on with 5.1.3 and figure out what the dependency is to be able to build it.

I've looked into this some more, and this definitely seems to be a consequence of the fix for SR-10707. SwiftPM expects that the headers are arranged as documented at Creating C Language Targets. But until the fix for SR-10707, SwiftPM didn't actually generate a modulemap according to the rules described in that documentation, so in practice, C modules that didn't have an umbrella header layout did not cause problems.

One way to address this is to create a `module.modulemap` file in the target — presence of a custom modulemap will prevent one from being automatically generated, and allows the package owner to customize how they want the headers in the target vended to clients.

In this case, it isn't clear to me what the vended headers should look like in order for Swift code to be able to see them. Which of the headers in the Protobuf target should be included in the module that's created for the target?

This should be addressed by #2813