Magnus Ulimoen
Magnus Ulimoen
@pansila That error is a bit mysterious, could you try getting a more verbose output with e.g. `cargo b --features vendor -vvv`?
If you don't have `libusb` installed you might have to configure `libusb` to also be vendored. You can do this by adding `features = ["vendored"]` under `uvc-src/Cargo.toml`.
I'm afraid using this for windows is not possible at the momen. The c library (which this crate wraps) does not support windows: https://github.com/libuvc/libuvc/issues/136. Workarounds exists, see that issue. If...
Occasionally magnled output is normal (see e.g. https://github.com/libuvc/libuvc/issues/122), and depends on the camera. You could file an issue towards `libuvc` if you would like to examine this in further detail....
Guess this is just an oversight or old API which deserves an upgrade. I would suggest for your crate to create a new error type wrapping the `None` from `sprs`...
`add_string_variable` was removed in preference to typing out the `netCDF` type explicitely. You can use the below as a replacement ```rust let mut reim = file.add_variable_with_type("reim", &["reim"], &netcdf::types::NcVariableType::String)?; reim.put_attribute("long_name", "Complex")?;...
This was removed at the same time as support for user-defined types were added. It felt redundant at the time to have so many constructors
See https://github.com/aldanor/hdf5-rust/issues/295 for an active fork
I suppose pinning to rust `1.75` is a pragmatic fix?
Could we alter CI to use an older macos runner for 1.8 and 1.10? 1.8 is still the only available hdf5 on some HPCs