What files from the target directory do the executable really need?

Question

After compiling my zagir program, the release folder is larger than 200 MB, which is ridiculous for the program I wrote. So I tried to check if only the zagir executable works, and he did it.

But the confusion is that the release folder also includes the libzagir.rlib file along with the .d files and the link of the other folders.

• What it is?
• Are they really needed?
• Am I going to get a runtime error when these files are ignored?
• What files should I link for a complete executable?

Cargo.toml

[package]
authors = ["Sharad Chand"]
name = "zagir"
version = "0.1.0"

[dependencies]
bcrypt = "0.1.3"
dotenv = "0.10.1"
image = "0.17.0"
log = "0.3.8"
r2d2 = "0.7.3"
r2d2-diesel = "0.16.0"
rand = "0.3.16"
rocket = "0.3.2"
rocket_codegen = "0.3.2"
serde = "1.0.11"
serde_derive = "1.0.11"
serde_json = "1.0.2"
validator = "0.6.0"
validator_derive = "0.6.0"

[dependencies.bigdecimal]
features = ["serde"]
version = "0.0.10"

[dependencies.chrono]
features = ["serde"]
version = "0.4.0"

[dependencies.diesel]
features = [
    "mysql",
    "chrono",
    "unstable",
    "numeric",
    "huge-tables",
]
version = "0.16.0"

[dependencies.diesel_codegen]
features = ["mysql"]
version = "0.16.0"

[dependencies.rocket_contrib]
features = ["handlebars_templates"]
version = "0.3.2"

[dependencies.uuid]
features = ["v4"]
version = "0.4"

Answer 1

What files from the target directory are really required by the executable

, . Rust .

- , Cargo, . , .

, :

• *.d - , Makefile
• *.rlib - Rust.
• build - .
• deps -
• examples - examples
• incremental -
• *-{hash} - cargo test
• -

Cargo.