Fix build and clippy checks when gdb features is enabled on windows

- The toolchain paths and flags are not correctly propagated on
  windows. When gdb feature is enabled, wasmtime-internal-jit-debug
  crate tries to compile C files using cc which is not correctly set
  on Windows

Signed-off-by: Doru Blânzeanu <dblnz@pm.me>

Author: dblnz

Justfile

@@ -72,6 +72,9 @@ fmt:
     cd src/wasm_runtime && cargo +nightly fmt -v --all
     cd src/hyperlight_wasm_macro && cargo +nightly fmt -v --all
 
+export CC_x86_64_unknown_none:= justfile_directory() / "src/wasm_runtime/guest-toolchain/clang"
+export AR_x86_64_unknown_none:= "llvm-ar"
+
 clippy target=default-target: (check target)
     cargo clippy --profile={{ if target == "debug" {"dev"} else { target } }} --all-targets --all-features -- -D warnings
     cd src/rust_wasm_samples &&  cargo clippy --profile={{ if target == "debug" {"dev"} else { target } }} --all-targets --all-features -- -D warnings

src/hyperlight_wasm/build.rs

@@ -134,6 +134,8 @@ fn build_wasm_runtime() -> PathBuf {
         .arg(&target_dir)
         .current_dir(&in_repo_dir)
         .env_clear()
+        // On windows when `gdb` features is enabled this is not set correctly
+        .env("CFLAGS_x86_64_unknown_none", "-fPIC")
         .envs(env_vars)
         .env("PATH", path_with(&toolchain_dir))
         .env("HYPERLIGHT_GUEST_TOOLCHAIN_ROOT", &toolchain_dir);