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
If a crate has plugin = true then any binaries crated by cargo test will depend on the DLL versions of Rust libraries instead of statically linking to them. If the directory containing the DLLs is not in PATH then the test binaries will fail to run. The most common way that this occurs is if the user is using rustup as recommended. So either rustup needs to make sure that directory is in PATH before forwarding to the actual cargo/rustc or cargo needs to make sure it adds that directory when running tests or possibly make tests statically link. The reason this is specific to Windows is because Windows does not have rpath, so the only way for the DLLs to be found is via PATH.
If a crate has
plugin = true
then any binaries crated bycargo test
will depend on the DLL versions of Rust libraries instead of statically linking to them. If the directory containing the DLLs is not inPATH
then the test binaries will fail to run. The most common way that this occurs is if the user is using rustup as recommended. So either rustup needs to make sure that directory is inPATH
before forwarding to the actual cargo/rustc or cargo needs to make sure it adds that directory when running tests or possibly make tests statically link. The reason this is specific to Windows is because Windows does not have rpath, so the only way for the DLLs to be found is viaPATH
.cc @brson
The text was updated successfully, but these errors were encountered: