aws-lc-sys dep cross-compile to Windows, CMake errors

[DavSanchez]

Hello!

Posting this here to see if I can get some help. I've been trying to cross-compile a project from x86_64-linux (and x86_64-darwin) to Windows following your FAQ related to aws-lc-sys and I've found this error:

Copying platform assembly files from /nix/store/swl1k131rzxw52mr1cklg28f4620g1mc-cargo-package-aws-lc-sys-0.32.2/aws-lc/generated-src/win-x86_64/crypto/ to /private/tmp/nix-build-newrelic_agent_control-deps-x86_64-w64-mingw32-1.1.0.drv-0/source/target/x86_64-pc-windows-gnu/release/build/aws-lc-sys-5d2288f8efea2754/out/build/aws-lc/crypto
  CMake Error: Could not open file for write in copy operation /nix/store/swl1k131rzxw52mr1cklg28f4620g1mc-cargo-package-aws-lc-sys-0.32.2/aws-lc/include/openssl/base.h.tmp
  CMake Error: : System Error: Permission denied
  CMake Error at aws-lc/CMakeLists.txt:1351 (configure_file):
    configure_file Problem configuring file


  CMake Error: Could not open file for write in copy operation /nix/store/swl1k131rzxw52mr1cklg28f4620g1mc-cargo-package-aws-lc-sys-0.32.2/aws-lc/include/openssl/opensslv.h.tmp
  CMake Error: : System Error: Permission denied
  CMake Error at aws-lc/CMakeLists.txt:1352 (configure_file):
    configure_file Problem configuring file
    

  thread 'main' panicked at /nix/store/pmdjrk1ifrcgbxkd37s4lniaysxbmmma-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/cmake-0.1.54/src/lib.rs:1119:5:

  command did not execute successfully, got: exit status: 1

  build script failed, must exit now
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

I get this is might not be an issue of crane itself but I don't know exactly how to fine-tune the way the dependencies are built, it seems that CMake is trying to write to files in the Nix store which of course would fail, though it seems that the purpose is to only copy them.

I'd say there'd be a way to instruct CMake to not attempt to open with write or to do so in a modifiable copy of the dependency sources during the build, but don't know exactly how. I find it weird that it's attempting to do this in the first place.

Have you found this before?

The flake output I'm trying to build is this one. Other cross-compiled outputs seem to be building fine (there's x86_64-linux-musl and aarch64-linux-musl that I'm able to run from macOS).

Thanks!

[DavSanchez]

Somehow this started working after one of our automated bumps of dependencies on Cargo.lock. Perhaps they fixed some issue on their side!