You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't investigated the exact cause, but when building for anything that isn't my native system (x86_64-unknown-linux-gnu), even though the foo-deps derivation is built and unpacked into the foo build directory, rust will recompile all the dependencies.
I have confirmed this to be the case with at least wasm32-unknown-unknown and x86_64-pc-windows-gnu.
I have an (untested) hunch that the problem may be as simple as follows: when you specify CARGO_BUILD_TARGET, compile artifacts are stored in e.g. target/x86_64-pc-windows-gnu/debug instead of target/debug. Perhaps the crane builder just needs to account for this.
I haven't investigated the exact cause, but when building for anything that isn't my native system (
x86_64-unknown-linux-gnu
), even though thefoo-deps
derivation is built and unpacked into thefoo
build directory, rust will recompile all the dependencies.I have confirmed this to be the case with at least
wasm32-unknown-unknown
andx86_64-pc-windows-gnu
.Naersk had the same problem too, which I solved in this PR nix-community/naersk#227.
I have an (untested) hunch that the problem may be as simple as follows: when you specify
CARGO_BUILD_TARGET
, compile artifacts are stored in e.g.target/x86_64-pc-windows-gnu/debug
instead oftarget/debug
. Perhaps the crane builder just needs to account for this.@yusdacra
The text was updated successfully, but these errors were encountered: