Where to place custom module.modulemap for third party C library without touching their source code

[Aciid (Ankit Aggarwal)]

@mman

But I have one C library that just publishes a couple of XXX/include/YYY.h files defining various features, without defining one big umbrella file, mainly because the library is intended to be used piece by piece by including only what is necessary. The swift package manager (I think) is not finding the umbrella header and therefore is not creating a clang module (I think) and Xcode later fails to compile swift sources that need access to the C code with the error:

SwiftPM always generates a modulemap for C libraries, even if they don't have an umbrella header. Try to find the generated modulemap in the .build directory. One possibility is that the module name generated for XXX could be normalized by SwiftPM. The import statement must mention the module name defined in the modulemap.

@mman

What's the best practice to swift-ify a third party C code without upstream modifications these days?

I've found symlinks to the files inside the submodule directory to work pretty well. The downside is that you have to create them by hand but you can automate that using some script.