-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Project with bootloader v0.11; Error while compiling kernel
, says std
is required by serde
#1240
Comments
kernel
, says std
is required by serde
kernel
, says std
is required by serde
Blog os required bootloader 0.9. It doesn't work with any later version of the bootloader crate as these rework the way building disk images is done. |
they are following the draft of edition 3 which uses 0.11 |
I see. I think this is a cargo bug in the bin deps feature. I would guess it unified features between the kernel itself and the crate that builds the disk image. |
For what it is worth, I have also been toying around with something akin to what is in the edition 3 branch. Here's my rust-toolchain.toml file from the root of my workspace. (Note: I'm on an arm macbook, as such I cannot remember if the target also needs to be specified here or not):
I suspect the part that is really worth sticking onto is the nightly version. EDIT: Also my Cargo.toml workspace file is using |
@kastermester Thank you so much!!! |
@Momijiichigo I would also recommend adding a
It's also worth considering pinning a specific nightly version in your toolchain file, and specifying your targets:
Both of these make it a bit more reliable for others cloning your repo to reproduce your environment. |
@torrancew thanks for the advice! |
As an alternative to |
I also wrote the details of this problem in this GitHub issue comment:
rust-lang/cargo#11772 (comment)
Error
The compiler throws error while compiling
kernel
, saying a dependencyserde
uses std whilekernel
is no_std:Info
kernel
isno_std
bindep artifact dependency, targetingx86_64-unknown-none
bootloader-x86_64-common
,Steps to reproduce error
cargo build
Comment
I don't know if this is a problem with cargo, but I posted this issue here just in case so that hopefully anyone here might be familiar with this problem and have solutions
The text was updated successfully, but these errors were encountered: