#cargo

is there a way of overriding the default target? e.g. if I want to cross compile from x86_64-unknown-linux-gnu to x86_64-unknown-linux-musl by default

sfackler: build.target in .cargo/config I think

ah thanks!

How do I build cargo standalone, now that the Cargo.lock was removed?

(for a distribution package)

can I somehow use the cargo.lock from the rustc source tree?

Could we `-Dwarnings` from the command line in Cargo?

We have a ton of integration tests, and adding `![deny(warnings)]` to each of them seems tiresome...

matklad: you can set `RUSTFLAGS="-D warnings"`

sfackler but that would affect my dependencies as well, right?

nope - cargo passes a --cap-lints to dependencies that overrides it

a -Dwarnings on cargo would be nice though

Hm, that sounds great, thanks a lto!

since the RUSTFLAGS approach is really subtle

Yeah

That's kinda an important workflow: you want to -Dwarnings on CI, but, at the same time, having warnings locally is OK

Is building cargo outside of the rustc build now unsupported?

bennofs_matrix: it works just fine in my experience?

well but there is no lockfile anymore...

you can still build it without a lockfile. if you want it to be reproducible you can save the lockfile off

or something like that

so that does not feel like a supported way to build cargo for release

or just build it via the rust src package

supported by who?

if the build doesn't work then that's a cargo bug for sure

I mean, building a cargo distribution package using a custom lock file is probably not such a good idea. Because then we are not really using the "upstream" deps and may hit different bugs

if you want to build the same thing that the official dists contain, then you should build from the rust source tarball

is it possible to build only cargo from that tarball? Or does cargo always need to match rustc version?

I think I'll just manually generate a lockfile, but it feels wrong to me as every other executable project usually comes with a lockfile itself