swift_c_module "does not have mandatory providers: 'cc'" with bazel 0.22 about rules_swift

[allevato]

I believe it's this: bazelbuild/bazel@a60b6ce

There have been a number of changes to the C++ providers recently that I've been waiting to become finalized enough that I can adopt them.

[keith]

Confirmed that setting --no incompatible_disable_legacy_cc_provider works around this

[keith]

Is this something we can migrate now? Or would we have to support both at once? I haven't looked for when the new providers were added

[keith]

It looks like the same conversation is happening here bazelbuild/bazel#7036 (comment)

[keith]

@allevato is this something you're planning on working on before the 0.22 release?

[allevato]

I'll start working on the migration this week, but the currently released version of Bazel that we use internally doesn't yet include the above commit yet, so I can't release anything until we catch up to that.

I looked into support both simultaneously, but the effort would be fairly large since the old- and new-style providers are very different, and I can't rationalize that amount of effort for a short-term workaround.

If Bazel releases 0.22 before I'm able to fully test the change internally and push it out, then I'd recommend using --noincompatible_disable_legacy_cc_provider until rules_swift can be updated.

[keith]

I've commented on the linked issue asking about the migration window, it doesn't seem like 0.22 has the necessary files I expected. I've submitted a first pass PR for this that is compatible with bazel HEAD right now #129

[keith]

My PR is green now so we should be good for compatibility with 0.22!

[allevato]

I believe this is resolved now.