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 automatic platform detection from inbound crosstool_top and cpu #2859

Merged
merged 2 commits into from Jul 1, 2021
Merged

Add automatic platform detection from inbound crosstool_top and cpu #2859

merged 2 commits into from Jul 1, 2021

Conversation

steeve
Copy link
Contributor

@steeve steeve commented Apr 3, 2021

Reopens #2451

When an inbound crosstool_top and cpu are specified, some platforms
can be automatically inferred/detected.

Some legacy rules still implement configuration splits on
crosstool_top and cpu instead of platform constaints. This is the
case most notably for rules_apple and rules_android.

Add a generic platform matching system based on crostool_top/cpu.

Finally, add Apple and Android matchers.

Refs #2443

When an inbound `crosstool_top` and `cpu` are specified, some platforms
can be automatically inferred/detected.

Some legacy rules still implement configuration splits on
`crosstool_top` and `cpu` instead of platform constaints. This is the
case most notably for rules_apple and rules_android.

Add a generic platform matching system based on `crostool_top`/`cpu`.

Finally, add Apple and Android matchers.

Signed-off-by: Steeve Morin <steeve@zen.ly>
The -framework flag needs to have its value in the same or clause.

This fixed boostraping stdlib on iOS.

Signed-off-by: Steeve Morin <steeve@zen.ly>
Copy link
Contributor

@jayconrod jayconrod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the slow review. Looks good.

@jayconrod
Copy link
Contributor

You should have merge power btw, so I'll leave it up to you to hit the button!

@jayconrod jayconrod merged commit 026db6d into bazelbuild:master Jul 1, 2021
fmeum added a commit to fmeum/rules_go that referenced this pull request Mar 1, 2023
fmeum added a commit to fmeum/rules_go that referenced this pull request Mar 1, 2023
fmeum added a commit to fmeum/rules_go that referenced this pull request Apr 19, 2023
…nd cpu (bazelbuild#2859)"

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
fmeum added a commit to fmeum/rules_go that referenced this pull request Apr 19, 2023
…nd cpu (bazelbuild#2859)"

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
fmeum added a commit to fmeum/rules_go that referenced this pull request Apr 19, 2023
…nd cpu (bazelbuild#2859)"

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
fmeum added a commit to fmeum/rules_go that referenced this pull request Apr 19, 2023
…nd cpu (bazelbuild#2859)"

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
fmeum added a commit that referenced this pull request Apr 19, 2023
…nd cpu (#2859)" (#3468)

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
tingilee pushed a commit to tingilee/rules_go that referenced this pull request Jul 19, 2023
…nd cpu (bazelbuild#2859)" (bazelbuild#3468)

This reverts commit 026db6d.

Bazel is migrating to platforms and toolchains resolution, but this
logic frequently reset platforms back based on the value of the
legacy `--cpu` and `--crosstool_top` flags. Instead, users of rules that
still rely on these flags should use the `platform_mappings` file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants