Building libcamera from the latest version of meta-or fails
the buildpaths qa check with a number of generated binaries.
Looking into the logs, it seemed that the -f*-prefix-map
flags were present to gcc invocations, but the used flags
were quite off for g++ invocations. It seems that using
the cpp_args meson option overwrites (at least most of)
the CXXFLAGS set by Yocto, including the -f*-prefix-map
flags.
To avoid this, append the extra compile flag to the
CXXFLAGS variable instead of using meson's cpp_args option.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
* libcamera was updated in meta-oe in:
https://git.openembedded.org/meta-openembedded/commit/?id=4e0281797277cf44287de93618c51e4a219fac75
* now it was failing with:
meson.build:3:0: ERROR: Options "raspberrypi" are not in allowed choices: "all, auto, imx8-isi, ipu3, rkisp1, rpi/vc4, simple, uvcvideo, vimc"
because raspberrypi support was updated and renamed to rpi/vc4 in:
726e9274ea
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Add Raspberry Pi pipeline handler and Image
Processing Algorithms.
Work around clang 14/15 build error:
field within 'v4l2_ext_control' is less aligned.
See
https://github.com/kbingham/libcamera/pull/40.
Signed-off-by: Devendra Tewari <devendra.tewari@gmail.com>
This is the result of automated script conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
libcamera middleware has supported many pipelines for video frames capturing.
So defined the packageconfig, to enable the rpi pipeline and to capture frames
using the rpi camera sensor.
Signed-off-by: Madhavan Krishnan <madhavan.krishnan@linaro.org>
