rules_swift icon indicating copy to clipboard operation
rules_swift copied to clipboard

Bazel rules to build Swift on Apple and Linux platforms

Results 147 rules_swift issues
Sort by recently updated
recently updated
newest added

The recent [rules_proto 6.0.0 release](https://github.com/bazelbuild/rules_proto/releases/tag/6.0.0) migrates `rules_proto_toolchains()` from `repositories.bzl` to `toolchains.bzl`. We need a migration path for [swift/extras.bzl](https://github.com/bazelbuild/rules_swift/blob/1aec64c218fc057c2a836e67bd55bc514e0ef8bb/swift/extras.bzl). Current: ``` load( "@rules_proto//proto:repositories.bzl", "rules_proto_dependencies", "rules_proto_toolchains", ) ``` Should be: ``` load("@rules_proto//proto:repositories.bzl",...

After spending quite some time on this, I determined that Swift incremental compilation via Bazel and rules_swift does not work. I am aware that there has been some progress made...

3rd party consumers of rules_swift may wish to create custom rules which behave similar to swift_library from the perspective of other rules and tools. Right now this is a fairly...

Likely coming from https://github.com/bazelbuild/rules_swift/blob/69df97201ef4274e87b68481fddadc87d8cb50c0/swift/toolchains/config/compile_config.bzl#L1450 includes all private and public transitive headers. Running `bazel aquery "deps(//examples/apple/objc_interop:Printer)"` confirms `Private.h` header that is in srcs (ie private) is part of inputs of `Compiling...

Replaces `experimental_mixed_langauge_library` in rules_apple. Meant to support SE-0403.

I'm a little curious, when using `swift_c_module`, the `.pcm` files emitted by swiftc would store some absolute paths, like the path of the modulemap, or the path of Xcode SDK,...

Extend the Windows CI to include the tests as well. This will mostly complete the Windows support (the remaining pieces remain in supporting the Windows ARM64 build host).

I am thinking about adding features to enable the three accepted combinations of `-strict-concurrency=` and wanted to check if this is useful to anybody else. My motivation: Configuring the `copt`...

`swift_test` targets can now shard their execution using Bazel's standard `shard_count` test attribute. When Bazel runs a sharded test, it spawns _N_ separate actions in parallel where each shard runs...

breaking change