We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was following the OS tutorial, and ran into an issue when using cargo bootimage.
cargo bootimage
→ cargo bootimage --target ./x64_86-darkos.json Building kernel Compiling compiler_builtins v0.1.105 Compiling core v0.0.0 (C:\Users\ticta\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core) Compiling bootloader v0.9.23 Compiling rustc-std-workspace-core v1.99.0 (C:\Users\ticta\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\rustc-std-workspace-core) Compiling os v0.1.0 (C:\Users\ticta\Deno\os) Finished dev [unoptimized + debuginfo] target(s) in 21.97s Error: Failed to find kernel binary in cargo metadata output
When looking through to target folder, it did spit out a file that looks to be the kernel binary:
Not exactly sure how to solve this issue.
My os is Windows (11) and my cargo version is cargo 1.77.0-nightly (1ae631085 2024-01-17)
cargo 1.77.0-nightly (1ae631085 2024-01-17)
The text was updated successfully, but these errors were encountered:
Also, my config.toml looks like this:
config.toml
[unstable] build-std-features = ["compiler-builtins-mem"] build-std = ["core", "compiler_builtins"] [build] target = "C:\\Users\\ticta\\Deno\\os\\x64_86-darkos.json"
Sorry, something went wrong.
No branches or pull requests
I was following the OS tutorial, and ran into an issue when using
cargo bootimage
.When looking through to target folder, it did spit out a file that looks to be the kernel binary:

Not exactly sure how to solve this issue.
My os is Windows (11) and my cargo version is
cargo 1.77.0-nightly (1ae631085 2024-01-17)
The text was updated successfully, but these errors were encountered: