Keith Smiley
Keith Smiley
How do you reproduce this? I tested on my M1 machine and building the toolchain directly, or the simple_make example works fine. Maybe because I have a full Xcode install...
It's possible that this was new with some Xcode / macOS release, I'm currently on macOS 12.2.1 and Xcode 13.2.1
@kaylathar mentioned offline that someone was looking at this, I believe it's just because the underlying apple_static_library isn't aware of any of these things
Note that having a test runner again would potentially help support code coverage as well. Although I'm sure there are downsides
What orchestration are you thinking for this case? I wonder if another approach would be to provide some library that could do this generation instead? I don't know rust very...
That doesn't seem to be the case, in our case when running all of our tests with bazel it would take >1 hour (I never waited for it to finish)...
Another case that's very similar to this is the environment.plist. This is built for each bundle, even though the result ends up being the same. For us this means we're...
This should fix the environment.plist issues https://github.com/bazelbuild/rules_apple/pull/522
Yes. The workarounds are either to use a rule like the one above, or set the same test host for all your test targets
Updated rule (click to expand) ```bzl """ This provides a resource bundle implementation that builds the resource bundle only once for iOS NOTE: This rule only exists because of this...