Thi Doan
Thi Doan
IIRC it was done like that so that we didn't have to change our import statements during the migration to Bazel. For example `@import MixedModule;` would also import the Swift...
> * [ ] A target needs to be created for each `proto_library` that is a transitive dependency of the `swift_proto_library`. A target shouldn't be made for `swift_proto_library` itself. How...
Given a swift_proto_library target and a cc_proto_library target both depend on a proto_library target, if an Xcode target is created for each proto_library, which type of source files should we...
The variable is optional, so it can run outside of Xcode, but we always run this with Xcode or `xcodebuild`.
That would work. But I don't really like to manage yet another git-ignored file. Is there a way to take certain environment variables and make them available in test? I...
I'll need to look a bit more but this was the only way that I saw it generated correctly in the Xcode project. ``` # .bazelrc build --test_env=MY_VAR=value ```
@Fresheyeball Open all graffle files at least once before running the script works for me.
cc @fmeum
@warlockosx What versions of Bazel and rules_apple/rules_swift are you using?