ABI compatibility with upstream libcamera

[carlodri]

Hi everyone, and thank you for your work on this library.

I am trying to build libcamera and its raspberry pi fork on the conda-forge ecosystem (see conda-forge/staged-recipes#29477). After landing these libraries I would also build picamera2.

This would have huge advantages for developers since it would allow mixing picamera2 with other conda-forge and pypi packages inside clean environments without messing with system python installations. It would also ensure that picamera2 is tightly coupled to the correct raspberrypi/libcamera version.

Now here comes my question: is this fork completely ABI-compatible with its upstream version? If yes we could build two package variants for libcamera that would be mutually exclusive and avoid name clashing and other mess.

Thanks in advance for your kind help!

[naushir]

Now here comes my question: is this fork completely ABI-compatible with its upstream version? If yes we could build two package variants for libcamera that would be mutually exclusive and avoid name clashing and other mess.

Yes, this fork is ABI compatible with the upstream libcamera. We do have some additional functionality in this release that is in the process of being merged upstream, but they are internal to libcamera, and will not change the ABI/API.

[carlodri]

Great, thank you @naushir!