-
Notifications
You must be signed in to change notification settings - Fork 402
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
Bare-Metal #256
Comments
Hi, Sorry for answering so late. Glad you are looking into that. We have a bunch of bindings here that defines the mapping between rust platform and various other property. uefi is unknown so either you need to update the system or (most probably) add it to the triple_mappings. |
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 3, 2021
Pursuand to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 3, 2021
Pursuand to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 17, 2021
Pursuand to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 30, 2021
Pursuand to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 30, 2021
Pursuant to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
cceckman
added a commit
to cceckman/rules_rust
that referenced
this issue
Jan 30, 2021
Pursuant to bazelbuild#256. - Add "cpu" constraint fulfillments for "riscv32imac" and "riscv64imac", matching the CPU strings available in the Rust toolchain for bare-metal builds. - Add mappings for the "none" OS constraint, which is available upstream in bazelbuild/platforms.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there, I have been trying out Rust with Bazel for while now and must say the experience is quite nice.
I want to start developing firmware utilities with Rust and Bazel. I'm trying to target the UEFI platform for now. I see there is a way to register toolchains for Rust inside Bazel, but it keeps giving me errors. The target triple I'm going for is
x86_64-unknown-uefi
but it keeps on throwing an error that it's not supported.Is it possible to develop bare metal targets with
rules_rust
?The full error log is below:
The text was updated successfully, but these errors were encountered: