From a469cef1abecbb0bb850f785ef6541792fdc9827 Mon Sep 17 00:00:00 2001 From: Dirk Gadsden Date: Sat, 23 Jan 2016 23:39:38 -0500 Subject: [PATCH] Clarify when `Cargo.lock` is created by `cargo build` in the book Also remove a "finally" in the section about building for release to make it feel a bit friendlier. --- src/doc/book/getting-started.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/doc/book/getting-started.md b/src/doc/book/getting-started.md index 18d5ca5be1a..77d468254b6 100644 --- a/src/doc/book/getting-started.md +++ b/src/doc/book/getting-started.md @@ -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