Keith Smiley
Keith Smiley
> Can you please point me to the doc for this? There aren't any docs for this tool, it's [private API](https://github.com/bazelbuild/rules_apple/blob/aa0b4843ed98ba1723e42ac88f54374d20b9fde2/apple/internal/BUILD#L29-L32) so really rules_ios shouldn't use it at all and...
I mean bundletool itself is the private API. Also anything in `internal` packages like these imports https://github.com/bazel-ios/rules_ios/blob/56dfa68d77cf77fd12ba6f5f8332e3913f5ab8c9/rules/precompiled_apple_resource_bundle.bzl?rgh-link-date=2022-04-01T21%3A52%3A08Z#L11-L17 (buildifier warns about this, but maybe that's not enabled on rules_ios CI?)
That's a configuration identifier generated by bazel itself
Also see https://github.com/bazelbuild/bazel/issues/12389
We should document common approaches to this since it comes up a lot
Can you include the full error report?
Interesting, I expected there to be more in that output. Can you test with HEAD of rules_apple and tulsi?
mediapipe depends on rules_apple, I just want to make sure it's a new enough version since you're using a new version of bazel
Huh I wonder what the default flag is, it looks like that build setting defaults to nothing, and passes `--optimization time` or `--optimization space` based on the value. Strangely I...
If you use a [`macos_command_line_application`](https://github.com/bazelbuild/rules_apple/blob/a5160afe1c05f5b52eb4df8e75a0fcec3ff47701/doc/rules-macos.md#macos_command_line_application) instead of a `cc_binary` does it work?