As described above. My use case is cross compiling a package to the x86_64-pc-windows-gnu target from Linux.
Everything seems to check out... but when it tries to dynamically load the .dll and call the function to get the version, it breaks for obvious reasons. For this use case, would it be possible to introduce an env variable to allow bypassing this check?
Another note: In this config, the library binary name is libhdf5.dll (build.rs checks for hdf5.dll only) and it dumps out in /bin instead of /lib. Would it be possible to specify the library binary path directly with an env var?
These two things seem relatively straightforward to implement, but let me know if you'd like me to open a PR.
As described above. My use case is cross compiling a package to the x86_64-pc-windows-gnu target from Linux.
Everything seems to check out... but when it tries to dynamically load the .dll and call the function to get the version, it breaks for obvious reasons. For this use case, would it be possible to introduce an env variable to allow bypassing this check?
Another note: In this config, the library binary name is libhdf5.dll (build.rs checks for hdf5.dll only) and it dumps out in /bin instead of /lib. Would it be possible to specify the library binary path directly with an env var?
These two things seem relatively straightforward to implement, but let me know if you'd like me to open a PR.