build faliling on windows due to "file not found

[solomoncyj]

build commit : 899fc76

> cargo build
   Compiling ring v0.17.12 (C:\Users\solom\Downloads\ring)
error: failed to run custom build command for `ring v0.17.12 (C:\Users\solom\Downloads\ring)`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `C:\Users\solom\Downloads\ring\target\debug\build\ring-52457b41425812e1\build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=CARGO_MANIFEST_DIR
  cargo:rerun-if-env-changed=CARGO_PKG_NAME
  cargo:rerun-if-env-changed=CARGO_PKG_VERSION_MAJOR
  cargo:rerun-if-env-changed=CARGO_PKG_VERSION_MINOR
  cargo:rerun-if-env-changed=CARGO_PKG_VERSION_PATCH
  cargo:rerun-if-env-changed=CARGO_PKG_VERSION_PRE
  cargo:rerun-if-env-changed=CARGO_MANIFEST_LINKS
  cargo:rerun-if-env-changed=RING_PREGENERATE_ASM
  cargo:rerun-if-env-changed=OUT_DIR
  cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ARCH
  cargo:rerun-if-env-changed=CARGO_CFG_TARGET_OS
  cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ENV
  cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ENDIAN
  cargo:rerun-if-env-changed=DEBUG
  cargo:rerun-if-env-changed=PERL_EXECUTABLE

  --- stderr
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/chacha/asm/chacha-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/chacha-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/aes/asm/aesni-gcm-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/aesni-gcm-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/aes/asm/aesni-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/aesni-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/aes/asm/ghash-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/ghash-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/aes/asm/vpaes-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/vpaes-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/bn/asm/x86_64-mont.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/x86_64-mont-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/bn/asm/x86_64-mont5.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/x86_64-mont5-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/ec/asm/p256-x86_64-asm.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/p256-x86_64-asm-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/sha/asm/sha512-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/sha512-x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/cipher/asm/chacha20_poly1305_x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/chacha20_poly1305_x86_64-nasm.asm"
  running "perl" "C:/\\/Users/solom/Downloads/ring/crypto/fipsmodule/sha/asm/sha512-x86_64.pl" "nasm" "C:/\\/Users/solom/Downloads/ring/target/debug/build/ring-1e602e94b5dc8ed8/out/sha256-x86_64-nasm.asm"
  running "./target/tools/windows/nasm/nasm" "-o" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\chacha-x86_64-nasm.o" "-f" "win64" "-i" "include/" "-i" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\" "-Xgnu" "-gcv8" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\chacha-x86_64-nasm.asm"

  thread 'main' panicked at build.rs:647:9:
  failed to execute ["./target/tools/windows/nasm/nasm" "-o" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\chacha-x86_64-nasm.o" "-f" "win64" "-i" "include/" "-i" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\" "-Xgnu" "-gcv8" "C:\\Users\\solom\\Downloads\\ring\\target\\debug\\build\\ring-1e602e94b5dc8ed8\\out\\chacha-x86_64-nasm.asm"]: The system cannot find the path specified. (os error 3)
  stack backtrace:
     0: std::panicking::begin_panic_handler
               at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library\std\src\panicking.rs:692
     1: core::panicking::panic_fmt
               at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library\core\src\panicking.rs:75
     2: build_script_build::run_command::{{closure}}
     3: core::result::Result<T,E>::unwrap_or_else
     4: build_script_build::nasm
     5: build_script_build::nasm
     6: build_script_build::generate_sources_and_preassemble
     7: build_script_build::AsmTarget::use_nasm
     8: build_script_build::AsmTarget::use_nasm
     9: core::ops::function::FnOnce::call_once
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

> --version

This is perl 5, version 40, subversion 2 (v5.40.2) built for MSWin32-x64-multi-thread

Copyright 1987-2025, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

> nasm --version
NASM version 2.16.03 compiled on Apr 17 2024

[solomoncyj]

Test-Path ./target/tools returns false...

[briansmith]

The crate published on crates.io already has the Windows x86/x86_64 assembly pre-assembled into object files so it skips the nasm steps. If you instead build from a Git checkout, you'll have to install nasm where build.rs expects it. As you discovered yourself, you don't have it installed there.

[solomoncyj]

why is it callling from a hard cocoded path isnted of the system one?