Closed tymurmustafaiev closed 1 month ago
We dont support rules_swift at master
yet (it will be a major version bump soon). I'll start working on fixing rules_ios to be compatible with it
Running a bisect shows this rules_swift commit as being first bad commit:
d68b21471e4e9d922b75e2b0621082b8ce017d11 is the first bad commit
commit d68b21471e4e9d922b75e2b0621082b8ce017d11 (HEAD, refs/bisect/bad)
Author: Tony Allevato <allevato@google.com>
Date: Mon Jan 24 08:30:10 2022 -0800
Copy `strict_includes` into `SwiftInfo` provider's Clang module descriptor in `swift_clang_module_aspect`.
This makes it so that the `apple_common.Objc` provider no longer needs to be handled separately for compilation by Swift build APIs. (It is still used for linking until that is migrated entirely onto `CcInfo`.)
PiperOrigin-RevId: 423822059
(cherry picked from commit 8ce95959d19334ce53963c6cbce3ac6eb40cd28c)
doc/api.md | 33 ++++++++-------------------------
swift/internal/compiling.bzl | 153 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------------------------------------
swift/internal/providers.bzl | 34 ++++++++++++----------------------
swift/internal/swift_clang_module_aspect.bzl | 27 ++++++++++++++++++++++-----
swift/internal/utils.bzl | 31 +++++++++++++++++--------------
5 files changed, 120 insertions(+), 158 deletions(-)
In my project I need to use latest changes from rules_swift. I'm trying to build framework using
apple_framework
rule for this target from test samples folder:When I try to build it - I got this error: 👇 ❌
However, building mixed language framework works fine ✅
How to reproduce
bzlmod
in.bazelrc
file:common --noenable_bzlmod
bazel_rules_swift
repo:maybe( git_repository, name = "build_bazel_rules_swift", commit = "8c144a2c28af3af7b78b5fd679550e6783a19194", remote = "https://github.com/bazelbuild/rules_swift.git", shallow_since = "1716513695 -0700", )