Is Cargo.lock wrong?

tools and infrastructure
1

I was wondering why cargo deny warns about Windows stuff, even though I’m on Linux. I found this comes from Cargo.lock indifferently listing unconfigured (and build) dependencies:

[[package]]
name = "stacker"
version = "0.1.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c886bd4480155fd3ef527d45e9ac8dd7118a898a46530b7b94c3e21866259fce"
dependencies = [
 "cc",
 "cfg-if",
 "libc",
 "psm",
 "winapi",
]

[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
 "winapi-i686-pc-windows-gnu",
 "winapi-x86_64-pc-windows-gnu",
]

[[package]]
name = "winapi-i686-pc-windows-gnu"
…

This comes from

…
[dependencies.psm]
version = "0.1.7"

[build-dependencies.cc]
version = "1.0.2"

[target."cfg(windows)".dependencies.winapi]
version = "0.3.6"
features = […

cargo tree shows what I suppose is really going on

├── lettre v0.11.7
│   ├── chumsky v0.9.3
│   │   ├── …
│   │   └── stacker v0.1.15
│   │       ├── cfg-if v1.0.0
│   │       ├── libc v0.2.155
│   │       └── psm v0.1.21
│   │           [build-dependencies]
│   │           └── cc v1.0.99
│   │       [build-dependencies]
│   │       └── cc v1.0.99
│   ├── …

Who’s right? I hope the last output. But then why does Cargo.lock have so much stuff which is not even in my build?

2

Cargo.lock has to be platform agnostic, otherwise it would change every time people on different platforms build, which would be unacceptable for a file meant to be checked in to your repository.

6 Likes
3

:+1:, that's exactly the issue here.

We've discussed one day supporting "this crate supports only these targets", and in that circumstance we could limit the contents of the lock. That would be useful for a variety of use cases. But in the absence of that, yeah, the lockfile has to support every target.

3 Likes
4

Hmm, annoying for code that will never come near Windows.

But no need for many ignores: deny.toml already had my target "x86_64-unknown-linux-musl" – I only needed to remove the comment and those warnings went away. :grinning:

2 Likes
5

See also Allow workspaces/crates to limit support to an explicit set of targets · Issue #11313 · rust-lang/cargo · GitHub.

1 Like
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.