Keith Smiley
Keith Smiley
Can folks who are interested test out https://github.com/bazelbuild/rules_apple/pull/1223 You'll still need to pass `--test_env=LCOV_MERGER=/usr/bin/true` But this generates a lcov file for consumption
Note you also have to pass `--experimental_use_llvm_covmap` always (at least for now https://github.com/bazelbuild/bazel/pull/13884)
This breaks the consumers of current_archs because it would need to strip the `sim_` prefix
There is some work that needs to be done in bazel core for this, for example the crosstool doesn't support it at all. I also imagine there's a few other...
I think the first step would be to add the CPUs to the bazel crosstool [here](https://github.com/bazelbuild/bazel/blob/86b800e4066389d4535fbdf280cfe9447b06df15/tools/osx/crosstool/cc_toolchain_config.bzl), then I think we'd have to create at least 1 new rule like `maccatalyst_application`...
How does this relate to https://github.com/bazelbuild/tulsi/pull/79 ?
so what commit of tulsi is this with now?
ah actually can you try HEAD from rules_swift with this
we probably need to create a new release for compatibility