Closed JohK closed 2 years ago
You need the default_info_init
branch of my fork at https://github.com/christianrauch/libcamera/tree/default_info_init. I submitted this to the libcamera-devel
mailing list and hope this gets merged soon.
Generally, I am tracking the most recent libcamera version and I am also rebasing the main
history until an initial release. If you continue to use this repo, you will have to hard reset from time to time.
Ok, understood. Thank you. I have to on another project first and will revisit my ROS setup in a few days, maybe I get lucky and it's already merged then. Is there a way on the official repo to follow merge requests?
Works as expected.
Ok, understood. Thank you. I have to on another project first and will revisit my ROS setup in a few days, maybe I get lucky and it's already merged then. Is there a way on the official repo to follow merge requests?
For the complete discussion, you have to watch the libcamera-devel
mailing list. To get an overview of the submitted patches, you can check out patchwork. E.g. the latest version of my patches is at https://patchwork.libcamera.org/project/libcamera/list/?series=3467. You can use the pwclient
to apply and test patches.
Unfortunately, everything works via mailing lists. There is no web interface to follow and contribute to discussions.
I have arducam-pivariety B0353 (AR0234) running on bullseye (verified with libcamera-raw).
Tried to run camera_ros (73f7cedf44d37a512688ac2ee0ac8069e7716a4e), but getting a runtime_error:
(Probably unrelated: The arducam wiki says not to worry about the missing .json file. Not sure if that is the right approach, but it didn't seem to bother libcamera-raw...)