rust-osdev / rust-osdev/bootloader
Question about the example
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Description
So in both the examples, -Zbuild-std=core is being passed from .cargo/config.toml. My question is how does that work with the boot/simple_bootsub crates that need std as well?
Or does the build options only apply to the main crate and not the boot sub crates as well?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting .cargo/config.toml and the boot/simple_boot subcrates to trace where -Zbuild-std=core is applied. Confirm whether the option reaches those subcrates, then make the examples or documentation explicitly explain its scope and expected std behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100