Clément Péron 35edaebc55 Revert "protobuf: stage protoc binary to sysroot" ... This reverts commit a0557fe543. As said by Ross[Ø]: "Putting the _target_ protoc into the sysroot for executation at _build_ time isn't useful because even if it has the right architecture, the tune might be incompatible. Recipes which want protoc should just depend on protobuf-native." This has been reverted recently by Samuli[1]: "If protoc is enabled for the build, recipes using protobuf will fail when protoc is not available in the recipe sysroot" Be the revert is incorret as This is an issue coming from qtgrpc other recipes that use protobuf or gRPC compiler, proplery looks for the binary in the correct sysroot folder. Qtgrpc recipe should fix this issue at the recipe level, for example this is what I've done for "etcd-cpp-apiv3" recipe[2] that doesn't need this patch to properly compile. So keeping this hack doesn't seems to be a correct fix. Note that qtgrpc recipe isn't available on meta-oe nor any other public layers. 0: https://patchwork.yoctoproject.org/project/oe/patch/20230904161230.377450-1-ross.burton@arm.com/ 1: https://patchwork.yoctoproject.org/project/oe/patch/20230927051101.3088498-1-samuli.piippo@qt.io/ 2: 47f0d9e032 CC: Samuli Piippo <samuli.piippo@gmail.com> CC: Ross Burton <ross.burton@arm.com> Signed-off-by: Clément Péron <peron.clem@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit bfb626a230) Signed-off-by: Armin Kuster <akuster808@gmail.com>		2023-10-12 09:58:05 -04:00
..
protobuf	protobuf: upgrade 4.22.2 -> 4.23.4	2023-10-04 07:52:48 -07:00
protobuf-c	protobuf-c: bump to next release to support protobuf 4.23.x	2023-10-04 07:52:48 -07:00
protobuf_4.23.4.bb	Revert "protobuf: stage protoc binary to sysroot"	2023-10-12 09:58:05 -04:00
protobuf-c_1.4.1.bb	protobuf-c: bump to next release to support protobuf 4.23.x	2023-10-04 07:52:48 -07:00