Closed brentleyjones closed 3 weeks ago
This fixes those "top-level" generated folders from our internal upstream project, and looks pretty good.
We have enough configs with sim+device times 3 product variants that there are 6 generated folders per library, so it's not a silver arrow for making things drop-dead-easy for Apple devs not fluent in Bazel, but it's also a big improvement over what we had previously.
What if we added an option to map a configuration name to something more idiomatic/familiar? ios_arm64-dbg-ios-arm64-min15.0-applebin_ios-ST-a79286d91b1b: iOS 15 Device Build
. It's manual & brittle as configurations change over time but is pretty flexible in naming?
We might be able to smartly translate those, since we know the platform, minOS, and arch for any given config by virtue of targets that have that config. So these could be named similar to how we do target disambiguation 🤔. That would be a followup PR though.
@erikkerber @sebastianv1 Can you approve if works for you locally?
Resolves #3037.