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
acrichto
sfackler: build.target in .cargo/config I think
sfackler
ah thanks!
Noldorin joined the channel
pcwalton joined the channel
cschneid joined the channel
cschneid has quit
cschneid joined the channel
Ericson2314 joined the channel
j0nthn has quit
Aaronepower has quit
Aaronepower joined the channel
pcwalton has quit
bennofs_matrix
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?
mattmccarty joined the channel
user2468 joined the channel
_Vi has quit
girafe joined the channel
pcwalton joined the channel
sleffy joined the channel
starblue joined the channel
pcwalton has quit
pcwalton joined the channel
Aaronepower has quit
sleffy has quit
Cldfire has quit
Cldfire joined the channel
pcwalton has quit
pcwalton joined the channel
matklad joined the channel
Aaronepower joined the channel
Aaronepower has quit
Aaronepower joined the channel
Aaronepower has quit
Aaronepower joined the channel
Aaronepower has quit
Aaronepower joined the channel
matklad
Could we `-Dwarnings` from the command line in Cargo?
pcwalton has quit
We have a ton of integration tests, and adding `![deny(warnings)]` to each of them seems tiresome...
sfackler
matklad: you can set `RUSTFLAGS="-D warnings"`
matklad
sfackler but that would affect my dependencies as well, right?
sfackler
nope - cargo passes a --cap-lints to dependencies that overrides it
a -Dwarnings on cargo would be nice though
matklad
Hm, that sounds great, thanks a lto!
sfackler
since the RUSTFLAGS approach is really subtle
matklad
Yeah
That's kinda an important workflow: you want to -Dwarnings on CI, but, at the same time, having warnings locally is OK
alx741 has quit
Aaronepower has quit
YuGiOhJCJ joined the channel
matklad has quit
pcwalton joined the channel
bennofs_matrix
Is building cargo outside of the rustc build now unsupported?
sfackler
bennofs_matrix: it works just fine in my experience?
bennofs_matrix
well but there is no lockfile anymore...
sfackler
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
bennofs_matrix
so that does not feel like a supported way to build cargo for release
sfackler
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
bennofs_matrix
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
sfackler
if you want to build the same thing that the official dists contain, then you should build from the rust source tarball
bennofs_matrix
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