Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move swift_usage_aspect and SwiftUsageInfo from rules_swift into rules_apple #1223

Merged

Conversation

brentleyjones
Copy link
Collaborator

With the toolchain information removed, this aspect/provider offers a minimal API. The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.

PiperOrigin-RevId: 439577534
(cherry picked from commit c24a84a)

brentleyjones referenced this pull request Jun 18, 2024
…rules_apple.

With the toolchain information removed, this aspect/provider offers a minimal API. The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.

PiperOrigin-RevId: 439577534
Copy link

google-cla bot commented Jun 18, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@brentleyjones brentleyjones changed the title Move swift_usage_aspect and SwiftUsageInfo from rules_swift into rules_apple Move swift_usage_aspect and SwiftUsageInfo from rules_swift into rules_apple Jun 19, 2024
…rules_apple

With the toolchain information removed, this aspect/provider offers a minimal API. The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.

PiperOrigin-RevId: 439577534
(cherry picked from commit c24a84a)
Signed-off-by: Brentley Jones <[email protected]>
@brentleyjones brentleyjones force-pushed the bj/cp-c24a84a128580b5cdd71e647dff01f7a6fe659c4 branch from 70a8db1 to 105cefc Compare June 19, 2024 22:45
@brentleyjones brentleyjones marked this pull request as ready for review June 19, 2024 22:46
@brentleyjones brentleyjones enabled auto-merge (rebase) June 19, 2024 22:46
@brentleyjones brentleyjones merged commit a790d9a into master Jun 19, 2024
14 checks passed
@brentleyjones brentleyjones deleted the bj/cp-c24a84a128580b5cdd71e647dff01f7a6fe659c4 branch June 19, 2024 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants