linux/meta-openembedded.git/meta-oe/recipes-devtools/protobuf, branch nanbield

Revert "protobuf: stage protoc binary to sysroot"

2023-10-12T13:58:05+00:00

This reverts commit a0557fe5433620717eeb00d3b16801711337b1a4. 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: https://github.com/etcd-cpp-apiv3/etcd-cpp-apiv3/commit/47f0d9e0326f3cc31c801a0ecf7312d1049ece3e CC: Samuli Piippo CC: Ross Burton Signed-off-by: Clément Péron Signed-off-by: Khem Raj (cherry picked from commit bfb626a23022d871ce3c0c64cb9e5d1cc17c737e) Signed-off-by: Armin Kuster

protobuf-c: bump to next release to support protobuf 4.23.x

2023-10-04T14:52:48+00:00

Signed-off-by: Clément Péron Signed-off-by: Khem Raj (cherry picked from commit f22a9adb44da3f97cb62c96ae2619a0306af6435) Signed-off-by: Armin Kuster

protobuf: upgrade 4.22.2 -> 4.23.4

2023-10-04T14:52:48+00:00

Bump protobuf to 4.23.4 to fix build with musl. Signed-off-by: Clément Péron Signed-off-by: Khem Raj (cherry picked from commit 39d8b9b7e6648d2c2cf33daac9be597e7d6f9dda) Signed-off-by: Armin Kuster

protobuf-c: add support of protobuf 4.22.x

2023-10-04T14:52:48+00:00

Signed-off-by: Xiangyu Chen Signed-off-by: Clément Péron Signed-off-by: Khem Raj (cherry picked from commit 802925894ab264de32e36f5843e9bf1a2aab90e3) Signed-off-by: Armin Kuster

protobuf: upgrade 3.21.12 -> 4.22.2

2023-10-04T14:52:48+00:00

Signed-off-by: Xiangyu Chen Signed-off-by: Clément Péron Signed-off-by: Khem Raj (cherry picked from commit fb34c7e3fae2ac7412dfb5920dfd1c9aca68427f) Signed-off-by: Armin Kuster

protobuf: stage protoc binary to sysroot

2023-10-04T14:52:48+00:00

If protoc is enabled for the build, recipes using protobuf will fail when protoc is not available in the recipe sysroot: | The imported target "protobuf::protoc" references the file | | ".../recipe-sysroot/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/usr/bin/protoc-3.21.5.0" | | but this file does not exist. Possible reasons include: | | * The file was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and contained | | ".../recipe-sysroot/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/usr/lib/cmake/protobuf/protobuf-targets.cmake" | | but not all the files it references. Use SYSROOT_DIRS to stage the binary to sysroot so it's always available for other recipes. Signed-off-by: Samuli Piippo Signed-off-by: Khem Raj (cherry picked from commit a0557fe5433620717eeb00d3b16801711337b1a4) Signed-off-by: Armin Kuster

Revert "protobuf: stage protoc binary to sysroot"

2023-09-07T15:22:43+00:00

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 reverts commit d7f46fa816964e30edb2ccfecc57a26251cc351c. Signed-off-by: Ross Burton Signed-off-by: Khem Raj

*.patch: add Upstream-Status to all patches

2023-06-21T16:15:20+00:00

There is new patch-status QA check in oe-core: https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a This is temporary work around just to hide _many_ warnings from optional patch-status (if you add it to WARN_QA). This just added Upstream-Status: Pending everywhere without actually investigating what's the proper status. This is just to hide current QA warnings and to catch new .patch files being added without Upstream-Status, but the number of Pending patches is now terrible: 5 (26%) meta-xfce 6 (50%) meta-perl 15 (42%) meta-webserver 21 (36%) meta-gnome 25 (57%) meta-filesystems 26 (43%) meta-initramfs 45 (45%) meta-python 47 (55%) meta-multimedia 312 (63%) meta-networking 756 (61%) meta-oe Signed-off-by: Martin Jansa Signed-off-by: Khem Raj

protobuf: upgrade 3.21.10 -> 3.21.12

2022-12-23T16:52:22+00:00

Changelog: ========== Fix broken enum ranges (#11171) Stop requiring extension fields to have a sythetic oneof (#11091) Python runtime 4.21.10 not works generated code can not load valid proto. Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

protobuf: upgrade 3.21.5 -> 3.21.10

2022-12-09T01:10:47+00:00

Signed-off-by: He Zhe Signed-off-by: Khem Raj