OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarify when Cargo.lock is created by cargo build in the book

Browse Source 
Also remove a "finally" in the section about building for release
to make it feel a bit friendlier.
This commit is contained in:
Dirk Gadsden 2016-01-23 23:39:38 -05:00
parent 0486e12ad0
commit a469cef1ab
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/doc/book/getting-started.md
View File

@ -511,15 +511,17 @@ programming languages. For complex projects composed of multiple crates, it’s
much easier to let Cargo coordinate the build. Using Cargo, you can run `cargo
build`, and it should work the right way.
## Building for Release
### Building for Release
When your project is finally ready for release, you can use `cargo build
When your project is ready for release, you can use `cargo build
--release` to compile your project with optimizations. These optimizations make
your Rust code run faster, but turning them on makes your program take longer
to compile. This is why there are two different profiles, one for development,
and one for building the final program you’ll give to a user.
Running this command also causes Cargo to create a new file called
### What Is That `Cargo.lock`?
Running `cargo build` also causes Cargo to create a new file called
*Cargo.lock*, which looks like this:
```toml