-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CC_Library without a tag does not generate a ModuleMap #1166
Comments
Is doing
|
Woops, apologies, I accidentally did not have my followup comment outside of the code portion. I'm looking to not have to set the tag at all, and instead have the module name be derived from the bazel target as per the documentation. |
based on this code rules_swift/swift/internal/swift_clang_module_aspect.bzl Lines 405 to 406 in da4eafe
cc_library dependencies. Can you add a repro case here (or better yet a failing test)
|
The CC Library looked like
Which upon adding to a swift_library as a dependency, no swiftmodule was created |
note that the behavior might differ for C vs C++, since until very recently Swift doesn't support C++ interop (and it's still disabled by default) |
I've successfully been able to have the modulemap generated when doing
instead |
In Swift_C_Module.bzl, the documentation mentions that
However, despite the documentation, not setting a tag leads to no modulemap being generated.
The text was updated successfully, but these errors were encountered: