Correct way to include dylib folder in search path for cargo run

[tangmi]

Problem/Steps

I'm trying to create a wrapper for a native library that includes a static .lib and two .dlls.

Following the Cargo Book docs on build scripts, I'm outputting (actual source):

cargo:rustc-link-lib=static=slang
cargo:rustc-link-search={path to .dll and .lib folder}

When I run cargo build --verbose, I see that subsequent calls to rustc include a flag -L {path to .dll and .lib folder}, but when running an example program using that library, the process exits fast with STATUS_DLL_NOT_FOUND. If I remove the call to the native library bindings and dump the PATH, my rustc-link-search path is not present (the search paths for bzip2-sys, curl-sys, and libz-sys do appear in PATH, but examining their respective build.rss and cc-rs's source, I couldn't figure out what they were doing differently).

I found cargo::util::paths::dylib_path(), but couldn't figure out where it was used...

Also, adding cargo:rustc-link-lib=dylib=slang-glslang makes Cargo complain about not being able to find slang-glslang.lib, which confuses me since I expect it to look for slang-glslang.dll and thought .lib was for static libs on Windows.

Edit: If I add cc::Build::new().out_dir(&slang_binaries_path).file("dummy.c").compile("foo") (where dummy.c is an empty file), I correctly get the PATH variable set.

Notes

Output of cargo version: cargo 1.33.0 (f099fe94b 2019-02-12)

Rust version:

stable-x86_64-pc-windows-msvc (default)
rustc 1.33.0 (2aa4c46cf 2019-02-28)

OS: Windows 10

Thanks for your time!

[tangmi]

I've figured this out, I was being to clever and passing the fs::canonicalized path and cargo:rustc-link-search does not like that.