Keith Smiley

Add/omit the HeadersPath Info.plist key for XCFramework with static libraries.

1

An XCFramework with static libraries can include public Objective-C(++) headers using the `public_hdrs` rule attribute, or generated headers from the underlying Swift module. This change updates the XCFramework Info.plist generation...

Remove apple_common.Objc provider linking

1

This involves: - Remove objc_provider input to new_executable_binary_provider - remove link info objc_provider input to framework providers - stop emitting ObjcProvider for purpose of linking info PiperOrigin-RevId: 512999312 (cherry picked...

Add swiftdocs to imported frameworks with swiftinterface files

1

swiftdoc files are produced when building things with -enable-library-evolution. If downstream IDE integrations want to grab them they should be propagated correctly so that that's possible.

New with Xcode 15 there is a new way to create strings files with a visual editor in Xcode. They are stored with all translations in a single json file...

-ObjC removal / transition plan

4

I'm creating this issue to track and document removing the `-ObjC` linker flag by default, and replacing that with enabling `alwayslink` by default on `swift_library`, `objc_library` and the other related...

Remove support to propagate frameworks via objc_library.runtime_deps

1

https://github.com/bazelbuild/rules_apple/commit/f711be032bd62fa13e866607bfb238e1988aca89 added support to propagate Apple frameworks using `data` rule attribute for both objc_library and swift_library targets. This change now removes support to propagate frameworks via `runtime_deps`. PiperOrigin-RevId: 514762665 (cherry...

Documentation revamp ideas

3

One idea is to do something like https://github.com/buildbuddy-io/rules_xcodeproj/blob/main/docs/usage.md which links out to larger examples but attempts to be the central place for discovering all the random features these rules support

Bazel removed runtime_deps https://github.com/bazelbuild/bazel/issues/17643 so we need to make some changes to be compatible with that, which involves cherry picking a big change to make data usable in the same...

llvm-covs path-equivalence flag is a bit strange. Everything is absolutized, including the paths in the binary, and the flag isn't consulted in the case the files exist. Because of this...

Remove `apple_common.Objc` provider usage related to linking now that the Apple linking logic in Bazel gets everything from `CcInfo`.

3

There are still a couple uses in `swift_clang_module_aspect` unrelated to linking that will be cleaned up separately. PiperOrigin-RevId: 503167994 (cherry picked from commit 19e48b97a7bc224bc5aff4e04fe2b42aabb5da8d)