-
Notifications
You must be signed in to change notification settings - Fork 13k
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 x.py check --stage 1
#46955
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Comments
pietroalbini
added
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
labels
Jan 30, 2018
Does #47460 do everything you wanted? |
I think it would need to be extended to support stage 1 to be useful for the case I outlined above. |
Is this fixed yet? |
This is sort of a hack, but you can do this by
I agree it would be great to support |
This was added in #81064. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
When modifying the interface between platform-specific/non-platform-specific parts of the codebase, proper testing requires being able to build for every supported target, which is very impractical. Ideally
x.py
would supportcargo check
such that platform specific code could still be validated and type checked without needing the corresponding cross-compiling C toolchains.This requires at least #44737 to be fixed to be useful.
The text was updated successfully, but these errors were encountered: