jgottula
commented
4 years ago I'm also working on an overhaul of some parts of libzwo_fixer, to make it more robust to failure in various ways. But I decided to keep that work separate from this branch and PR for now, since it's a bit half-baked at the moment.
(I'm realizing now that I'm probably wasting my time with this other effort: because ultimately it barely makes a difference whether libzwo_fixer safely tells you that there's been some kind of flagrant unrecoverable problem and it can't do its job properly, versus if it just crashes or makes the program linking to it exit with non-zero status. Because what actual sane reasonable recourse do you realistically have if libzwo_fixer runs into a problem and can't fix the brokenness? (Assuming that it doesn't have an error that crashes the program anyway.) Just keep going and happily continue with horrendous USB interruptions affecting the framerate? I dunno. I just sort of get the feeling that I'm overengineering something that doesn't really need to be engineered at all.)
From my quick inspection, I don't believe there are any changes in this new SDK version that substantially affect us. (No API changes, nothing different about the libusb idiocy that I could see.)
But nevertheless, the changelog for the new version nebulously asserts that it "Fix some bug". So, this PR updates everything to the new version.
I have also pushed an updated version of our libasicamera2 DEB package to the APT repository.
@bgottula You'll want to have
aptgrab the latest repo data and upgrade the libasicamera2 package on nix. And then explicitly rebuild the Python SWIG bindings. Because the SWIG stuff just kinda cluelessly builds against "whatever libASICamera2 headers and libraries are in the system directories" without regard for what version happens to be there.