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

Mention in the first post that our crate uses the 2018 edition

Browse Source
This commit is contained in:
Philipp Oppermann
2018-11-18 15:00:52 +01:00
parent ba31b21661
commit bf413d3baa
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
blog/content/second-edition/posts/01-freestanding-rust-binary/index.md
View File

@@ -52,10 +52,12 @@ By default, all Rust crates link the [standard library], which depends on the op
We start by creating a new cargo application project. The easiest way to do this is through the command line:
```
> cargo new blog_os --bin
> cargo new blog_os --bin --edition 2018
```
I named the project `blog_os`, but of course you can choose your own name. The `--bin` flag specifies that we want to create an executable binary (in contrast to a library). When we run the command, cargo creates the following directory structure for us:
I named the project `blog_os`, but of course you can choose your own name. The `--bin` flag specifies that we want to create an executable binary (in contrast to a library) and the `--edition 2018` flag specifies that we want to use the [2018 edition] of Rust for our crate. When we run the command, cargo creates the following directory structure for us:
[2018 edition]: https://rust-lang-nursery.github.io/edition-guide/rust-2018/index.html
```
blog_os