We’d like to make users aware of some important changes coming in the next imminent release of rpicam-apps.
As mentioned in this forum post from a couple of years ago, we have provided symbolic links from the legacy application and library names: to the updated naming scheme: These symlinks will be removed in the upcoming release.
This means that any usage of the old libcamera-* names will no longer work. If you are building, installing, or running rpicam-apps, please make sure to update your scripts and workflows to use the rpicam-* naming convention. Our documentation has followed this scheme for several years now, so if you're unsure, that's the best reference.
Additionally, the next release introduces a change to .so file naming and versioning that may affect users building custom applications with the rpicam-apps framework. The shared object file will now follow standard Debian conventions and be named: and the so library version numbering will follow the major version number only as is standard practice.
As mentioned in this forum post from a couple of years ago, we have provided symbolic links from the legacy application and library names:
Code:
libcamera-*Code:
rpicam-*This means that any usage of the old libcamera-* names will no longer work. If you are building, installing, or running rpicam-apps, please make sure to update your scripts and workflows to use the rpicam-* naming convention. Our documentation has followed this scheme for several years now, so if you're unsure, that's the best reference.
Additionally, the next release introduces a change to .so file naming and versioning that may affect users building custom applications with the rpicam-apps framework. The shared object file will now follow standard Debian conventions and be named:
Code:
librpicam-apps.soStatistics: Posted by naushir — Mon Jul 14, 2025 9:44 am — Replies 0 — Views 45