bazel: Migrate to the native x86_64-unknown-none build target
#14
Labels
Comments
SlyMarbo
added
enhancement
SlyMarbo
added a commit
that referenced
this issue
Apr 15, 2022
We will then be able to use the build artefacts within for the standard library, rather than needing to fetch them from source and build them locally. See #14. Signed-off-by: SlyMarbo <the.sly.marbo@googlemail.com>
SlyMarbo
added a commit
that referenced
this issue
Apr 15, 2022
Now that we have the pre-built copies of the Rust standard library for x86_64-unknown-none, we can use those instead of fetching libcore and liballoc with the host copy of Rust and fetching compiler_builtins directly. We also don't need to build them any more. This takes us part of the way to getting cross-compiling for free with rules_rust. See #14. Signed-off-by: SlyMarbo <the.sly.marbo@googlemail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that
x86_64-unknown-noneis a Tier 2 target (see rust-lang/rust#95705), we should be able to fetch it as a pre-built release. At the very least, this should mean we no longer need to fetch the standard library sources, build libcore and liballoc (and possibly compiler-builtins too). They should be replaced automatically by specifyingx86_64-unknown-noneinextra_target_triplesinrust_register_toolchains.If we're really lucky, it might even be possible to drop the entire cross-compiling toolchain for Rust. That would simplify things significantly.
The text was updated successfully, but these errors were encountered: