michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-17 06:47:49 +00:00
Code Issues Projects Releases Wiki Activity

Add link to custom targets (#857)

Browse Source 
This makes it slightly easier to find out more about the JSON file that specifies custom targets.
This commit is contained in:
Brian Kung
2020-09-21 08:20:00 -05:00
committed by GitHub
parent 685b8a94ac
commit 8ff1aeb96d
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
blog/content/second-edition/posts/02-minimal-rust-kernel/index.md
View File

@@ -104,8 +104,9 @@ Cargo supports different target systems through the `--target` parameter. The ta
[target triple]: https://clang.llvm.org/docs/CrossCompilation.html#target-triple [target triple]: https://clang.llvm.org/docs/CrossCompilation.html#target-triple
[ABI]: https://stackoverflow.com/a/2456882 [ABI]: https://stackoverflow.com/a/2456882
[platform-support]: https://forge.rust-lang.org/release/platform-support.html [platform-support]: https://forge.rust-lang.org/release/platform-support.html
[custom-targets]: https://doc.rust-lang.org/nightly/rustc/targets/custom.html
For our target system, however, we require some special configuration parameters (e.g. no underlying OS), so none of the [existing target triples][platform-support] fits. Fortunately, Rust allows us to define our own target through a JSON file. For example, a JSON file that describes the `x86_64-unknown-linux-gnu` target looks like this: For our target system, however, we require some special configuration parameters (e.g. no underlying OS), so none of the [existing target triples][platform-support] fits. Fortunately, Rust allows us to define [our own target][custom-targets] through a JSON file. For example, a JSON file that describes the `x86_64-unknown-linux-gnu` target looks like this:
```json ```json
{ {