[lib] is not copied over in Cargo.toml

[rbozan]

Might be related to #263

Having a Cargo.toml like the following:

[package]
name = "scenario"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["dylib"] # <-- I'm specifying that I want a dynamic library here (.so)

[dependencies]
scenario_builder = { git = "ssh://[email protected]/l4010/scenario_builder.git", features = ["build-scenario"] }
tokio = { version = "1.17.0", features = [ "macros" ] }
anyhow = "1.0.66"

sqlx = { version = "0.5", features = [ "runtime-tokio-rustls", "mysql" ] }

However looking in dummy-src the Cargo.toml now suddenly is:

[dependencies]
anyhow = "1.0.66"
"scenario_builder" = { features = [ "build-scenario" ], git = "ssh://[email protected]/l4010/scenario_builder.git" }
sqlx = { features = [ "runtime-tokio-rustls", "mysql" ], version = "0.5" }
tokio = { features = [ "macros" ], version = "1.17.0" }
[package]
edition = "2021"
name = "scenario"
version = "0.1.0"

Removing the whole [lib] block and crate-type. This results in NOT building a ".so" file but a ".rlib" file.

[06kellyjac]

copyLibs = true;?

naersk/README.md

Line 218 in 6944160

| `copyLibs` | When true, the resulting binaries are copied to `$out/lib`. <br/> Note: this relies on cargo's `--message-format` argument, set in the default `cargoBuildOptions`. Default: `false` |

[rbozan]

copyLibs = true;?

naersk/README.md

Line 218 in 6944160

| `copyLibs` | When true, the resulting binaries are copied to `$out/lib`. <br/> Note: this relies on cargo's `--message-format` argument, set in the default `cargoBuildOptions`. Default: `false` |

no that does not help. like I said, it does build a .rlib file as it seems it removes the whole [lib] block I specified .
copyLibs would indeed copy .rlib. but I did not want a .rlib, I wanted a .so file.