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

Add stubs for the Xcode rules in apple_support, for eventual migration from Bazel. #312

Conversation

keith
Copy link
Member

@keith keith commented Mar 4, 2024

This change only stubs out rules; providers and flags will come later. The providers in particular need some more thought before locking down their names, since the current names (like apple_common.XcodeVersionConfig) don't meet Starlark provider naming conventions.

PiperOrigin-RevId: 612472977
(cherry picked from commit 2177431)

…n from Bazel.

This change only stubs out rules; providers and flags will come later. The providers in particular need some more thought before locking down their names, since the current names (like `apple_common.XcodeVersionConfig`) don't meet Starlark provider naming conventions.

PiperOrigin-RevId: 612472977
(cherry picked from commit 2177431)
keith referenced this pull request Mar 4, 2024
…n from Bazel.

This change only stubs out rules; providers and flags will come later. The providers in particular need some more thought before locking down their names, since the current names (like `apple_common.XcodeVersionConfig`) don't meet Starlark provider naming conventions.

PiperOrigin-RevId: 612472977
@keith keith merged commit d59a3e0 into master Apr 3, 2024
12 checks passed
@keith keith deleted the ks/add-stubs-for-the-xcode-rules-in-apple_support-for-eventual-migration-from-bazel branch April 3, 2024 18:18
@keith
Copy link
Member Author

keith commented Apr 3, 2024

relevant upstream change being worked on bazelbuild/bazel@26c6add

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.

4 participants