Skip to content
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

How to use custom bootloader #59

Open
spcan opened this issue May 20, 2020 · 3 comments
Open

How to use custom bootloader #59

spcan opened this issue May 20, 2020 · 3 comments

Comments

@spcan
Copy link

spcan commented May 20, 2020

In the README of bootimage, it says that a custom bootloader is supported, but reading the linked page does not really clear up what should be done to do this.

Should I fork locally the bootloader crate, do my modifications and use it in my Cargo.toml as this? If not how should it be done?

[dependencies.bootloader]
version = "*"
path = "../bootloader"
@phil-opp
Copy link
Member

Unfortunately our support for custom bootloaders is still very experimental The main reason is that we did not define the interface between bootimage and bootloader crates yet, which means that e.g. the build instructions used for building the bootloader might still change.

So starting from a fork of bootloader is the best approach for now. The dependency kind (crates.io/git/local path) does not matter, as long as the dependency is named "bootloader". For crates with a different name, you can use cargo's support for renaming dependencies.

@spcan
Copy link
Author

spcan commented May 21, 2020

Great. I'll try this. Is there any plans on formalizing the bootimage interactions with custom bootloader crates (in the near future)? Just curious, not something really needed by me.

@phil-opp
Copy link
Member

Not in the near term. I think we want to first add support for UEFI and multiboot to the bootloader, which might require some changes to the build system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants