rules_swift
rules_swift copied to clipboard
Bazel rules to build Swift on Apple and Linux platforms
This mimics the behavior of `cc_library`. When consuming `CcInfo` from a `swift_library`, if the library is in an external repo, the `quote_includes` paths are not set. In the case of...
This breaks IDE integrations. I imagine it's a Swift change that we should fix upstream, or workaround in the worker. Related https://github.com/bazelbuild/tulsi/issues/262
This is a step towards removing it entirely. PiperOrigin-RevId: 406230375 (cherry picked from commit d1ba795ff479881bf14ba70294693dcabace4fd4)
In some cases the default `-D` flags are not desirable since users prefer to control them themselves.
Up until now rules_swift only exposed `protoc-gen-swiftgrpc`, the 0.x gRPC generated for Swift. This PR adds support for the 1.x gRPC generator, `protoc-gen-grpc-swift`. `protoc-gen-grpc-swift` generates code that depends on `GPRC`...
Right now, we only support kind-of-static linking: the `swift_library` targets that the binary depends on are statically linked into the final binary, but the Swift runtime libraries are dynamically linked....
There are quite a few features at this point that are useful to different folks. It would be useful for new users to see what is available so they can...
Typically when my co-workers and I are picking between `-O` and `-Osize`, we think about it at the app level and not the module level. If one wants to use...
i have proto file: path: app/a/api.proto path: app/b/api.proto with [swift_proto_library] ,It fails :0: note: filenames are used to distinguish private declarations with the same name :0: error: filename "api.pb.swift" used...
Hi, I'm trying to build a fairly complex app, which has a mix of Swift and Objective-C. The Swift code relies heavily on a bridging header, which itself imports a...