documentation request: what does `cargo install` do to build that `cargo build` doesn't?

[bwo]

Problem

I just encountered a very puzzling issue where cargo build would successfully build a binary but cargo install would fail during linking (specifically the linker would complain about not being able to find a name only defined in ssl3). Presumably different flags are being passed at some point, somewhere … but what? Even running cargo build in the project directory, then leaving it to run cargo install, would do a partial rebuild (and would fail).

Proposed Solution

No response

Notes

No response

[epage]

One difference explicitly listed in the documentation is that the lockfile is not used by default and you need to pass --locked to do so.

Something left between the lines in the docs is that it does a release build by default (because there is a --debug flag).