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
It seems that my build is statically linking HDF5 but not MSV CRT and that causes a problem?
I get a ton of errors like this:
libhdf5_metno_sys-afead0c756f87c12.rlib(H5EAstat.obj) : error LNK2001: unresolved external symbol __imp__wassert
libhdf5_metno_sys-afead0c756f87c12.rlib(H5FAstat.obj) : error LNK2001: unresolved external symbol __imp__wassert
libhdf5_metno_sys-afead0c756f87c12.rlib(H5HFdtable.obj) : error LNK2001: unresolved external symbol __imp__wassert
I want to
Statically link HDF5 because I absolutely don't want my users to have to find the right headers and I don't want to bundle them either, I need to not deal with that headache at all.
Summary
It seems that my build is statically linking HDF5 but not MSV CRT and that causes a problem?
I get a ton of errors like this:
I want to
Statically link HDF5 because I absolutely don't want my users to have to find the right headers and I don't want to bundle them either, I need to not deal with that headache at all.
Works with how I normally build, see this CI run:
https://github.com/luftkode/logviewer-rs/actions/runs/11369355310/job/31626596049
But with my release (cargo-dist) workflow
... the windows build fails: https://github.com/luftkode/logviewer-rs/actions/runs/11369355557/job/31626621637
I tried
Adding this
.cargo/config.toml
:does not change anything.
The text was updated successfully, but these errors were encountered: