Error while updating sources using "$ opkg update". [ opkg_verify_gpg_signature: GPG signature checking not supported ] [ pkg_src_verify: Signature verification failed for *. ]
#yocto
#raspberrypi
tokuchiprime@...
Hi everyone.
I am trying to setup a Package Feed with signed ipk packages. For this, I first set up the key pair on my build host.
This is the result of "$ gpg --list-keys" : /home/<username>/.gnupg/pubring.kbx
--------------------------------
pub rsa3072 2021-05-26 [SC] [expires: 2023-05-26]
<40-char-hex-key-id>
uid [ultimate] <user-id> <email-id>
sub rsa3072 2021-05-26 [E] [expires: 2023-05-26]
I added the following to my local.conf : # For generating signed packages
INHERIT += "sign_ipk"
IPK_GPG_NAME = "<last-8-digits-of-key-id>"
IPK_GPG_PASSPHRASE_FILE = "/home/<username>/passphrase.txt"
INHERIT += "sign_package_feed"
PACKAGE_FEED_GPG_NAME = "<last-8-digits-of-key-id>"
PACKAGE_FEED_GPG_PASSPHRASE_FILE = "/home/<username>/passphrase.txt"
Burnt the new image onto the SD Card and booted up. At this point, $ opkg update fails with the following error:
Downloading http://192.168.0.8/rpi_packages/all/Packages.gz.
Downloading http://192.168.0.8/rpi_packages/all/Packages.asc.
Downloading http://192.168.0.8/rpi_packages/cortexa7t2hf-neon-vfpv4/Packages.gz.
Downloading http://192.168.0.8/rpi_packages/cortexa7t2hf-neon-vfpv4/Packages.asc.
Downloading http://192.168.0.8/rpi_packages/raspberrypi3/Packages.gz.
Downloading http://192.168.0.8/rpi_packages/raspberrypi3/Packages.asc.
Collected errors:
* opkg_verify_gpg_signature: GPG signature checking not supported
* pkg_src_verify: Signature verification failed for all.
* opkg_verify_gpg_signature: GPG signature checking not supported
* pkg_src_verify: Signature verification failed for cortexa7t2hf-neon-vfpv4.
* opkg_verify_gpg_signature: GPG signature checking not supported
* pkg_src_verify: Signature verification failed for raspberrypi3.
The /etc/pki/packagefeed-gpg directory has PACKAGEFEED-GPG-KEY-b2qt-dunfell in it.
At first gnupg wasn't installed on the target, so I added it.
Running "$ gpg --list-keys" outputs:
gpg: directory '/home/root/.gnupg' created
gpg: keybox '/home/root/.gnupg/pubring.kbx' created
gpg: /home/root/.gnupg/trustdb.gpg: trustdb created
I imported /etc/pki/packagefeed-gpg/PACKAGEFEED-GPG-KEY-b2qt-dunfell, after which "$ gpg --list-keys" shows the public key. But it doesn't solve the issue.
Found a question in the mailing list, where the OP used OPKG_KEYRING_KEYS. So I rebuilt the image with OPKG_KEYRING_KEYS = "<last-8-digits-of-key-id>", but the result was same as earlier.
If signature verification is disabled then the sources are updated without any error. Thanks for reading.
|
|
a recipe that launches a docker container to build a custom library...
flobro30101@...
Has anyone seen suck an animal before, and if not, how hard would it be to launch a container, then get the output to install like a normal recipe does?
|
|
Re: Making a recipe that enables a systemd service it doesn't provide
Joshua Watt
It might be easier to manually enable the service with a
symbolic link instead of using systemd.bbclass with something
like: do_install() { install -Dm 755
${D}${systemd_unitdir}/system/multi-user.target.wants/ ln -s ${systemd_unitdir}/system/openvpn@.service
${D}${systemd_unitdir}/system/multi-user.target.wants/openvpn@... } NOTE: I didn't explicitly test this
On 5/27/21 9:17 AM, François GOUDAL
wrote:
Hello, I am struggling with something I couldn’t find any solution for so far. I am trying to make a very simple recipe that does this: - Drop an openvpn configuration file in /etc/openvpn/test.conf - Make the systemd service openvpn@... enabled by default The recipe itself depends on openvpn, and so, it doesn’t, by itself, provide the openvpn@.service , which comes with openvpn. Dropping the openvpn configuration file in the rootfs is easy, but I can’t manage to make the recipe to enable the service. I’ve tried adding this to my recipe: inherit systemd SYSTEMD_AUTO_ENABLE = "enable" SYSTEMD_SERVICE_${PN} = "openvpn@..." But bitbake fails on this recipe with the message below: ERROR: test-openvpn-config-1.0-r0 do_package: SYSTEMD_SERVICE_test-openvpn-config value openvpn@... does not exist I believe this is caused by the fact that the service file is not part of the files installed by the recipe itself, but it is not meant to be anyway. Is there a (clean) way to achieve this ? Thanks in advance
|
|
Re: Making a recipe that enables a systemd service it doesn't provide
Quentin Schulz
Hi François,
On Thu, May 27, 2021 at 02:17:03PM +0000, François GOUDAL wrote: Hello,Yes that seems like the origin of the error. Recipe data is local to the recipe. You therefore also cannot modify the openvpn recipe from another recipe (this includes enabling a service for example). The proper way to do it is to create a bbappend for the openvpn recipe and enable the service from there. SYSTEMD_AUTO_ENABLE = "enable" should be enough, though it'll start the loopback client and server unit too. It is not possible to have different image recipes enable or not the service, if this is something you want, you need to modify SYSTEMD_AUTO_ENABLE of the openvpn recipe in a configuration file (and the proper way is in a distro configuration file). Cheers, Quentin
|
|
Making a recipe that enables a systemd service it doesn't provide
François GOUDAL
Hello,
I am struggling with something I couldn’t find any solution for so far. I am trying to make a very simple recipe that does this: - Drop an openvpn configuration file in /etc/openvpn/test.conf - Make the systemd service openvpn@... enabled by default The recipe itself depends on openvpn, and so, it doesn’t, by itself, provide the openvpn@.service , which comes with openvpn. Dropping the openvpn configuration file in the rootfs is easy, but I can’t manage to make the recipe to enable the service. I’ve tried adding this to my recipe: inherit systemd SYSTEMD_AUTO_ENABLE = "enable" SYSTEMD_SERVICE_${PN} = "openvpn@..." But bitbake fails on this recipe with the message below: ERROR: test-openvpn-config-1.0-r0 do_package: SYSTEMD_SERVICE_test-openvpn-config value openvpn@... does not exist I believe this is caused by the fact that the service file is not part of the files installed by the recipe itself, but it is not meant to be anyway. Is there a (clean) way to achieve this ? Thanks in advance
|
|
[PATCH yocto-autobuilder-helper] config.json: transition ptests to minimal-based images
Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@...>
--- config.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index cf62815..2ccd24a 100644 --- a/config.json +++ b/config.json @@ -95,16 +95,16 @@ }, "ptest-qemu" : { "BUILDINFO" : true, - "BBTARGETS" : "core-image-sato-ptest", - "SANITYTARGETS" : "core-image-sato-ptest:do_testimage", + "BBTARGETS" : "core-image-ptest-all", + "SANITYTARGETS" : "core-image-ptest-all:do_testimage", "extravars" : [ "TEST_SUITES = 'ping ssh ptest'" ] }, "ptest-qemu-fast" : { "BUILDINFO" : true, - "BBTARGETS" : "core-image-sato-ptest-fast", - "SANITYTARGETS" : "core-image-sato-ptest-fast:do_testimage", + "BBTARGETS" : "core-image-ptest-fast", + "SANITYTARGETS" : "core-image-ptest-fast:do_testimage", "extravars" : [ "TEST_SUITES = 'ping ssh ptest'" ] @@ -124,7 +124,7 @@ "arch-hw" : { "BUILDINFO" : true, "step1" : { - "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-sato-ptest core-image-sato:do_populate_sdk", + "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-ptest-all core-image-sato:do_populate_sdk", "SANITYTARGETS" : "core-image-sato:do_testsdk" } }, @@ -344,7 +344,7 @@ }, "step2" : { "MACHINE" : "qemux86-64", - "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-sato-sdk-ptest core-image-sato:do_populate_sdk", + "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-ptest-all core-image-sato:do_populate_sdk", "SANITYTARGETS" : "core-image-sato:do_testsdk" }, -- 2.31.1
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.8.rc1)
Sangeeta Jain
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.8.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion is next Monday, May 31. Thanks, Sangeeta
-----Original Message-----
|
|
[PATCH yocto-autobuilder-helper] config.json: transition ptests to minimal-based images
Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@...>
--- config.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index cf62815..a850dd6 100644 --- a/config.json +++ b/config.json @@ -95,16 +95,16 @@ }, "ptest-qemu" : { "BUILDINFO" : true, - "BBTARGETS" : "core-image-sato-ptest", - "SANITYTARGETS" : "core-image-sato-ptest:do_testimage", + "BBTARGETS" : "core-image-minimal-ptest-all", + "SANITYTARGETS" : "core-image-minimal-ptest-all:do_testimage", "extravars" : [ "TEST_SUITES = 'ping ssh ptest'" ] }, "ptest-qemu-fast" : { "BUILDINFO" : true, - "BBTARGETS" : "core-image-sato-ptest-fast", - "SANITYTARGETS" : "core-image-sato-ptest-fast:do_testimage", + "BBTARGETS" : "core-image-minimal-ptest-fast", + "SANITYTARGETS" : "core-image-minimal-ptest-fast:do_testimage", "extravars" : [ "TEST_SUITES = 'ping ssh ptest'" ] @@ -124,7 +124,7 @@ "arch-hw" : { "BUILDINFO" : true, "step1" : { - "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-sato-ptest core-image-sato:do_populate_sdk", + "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-minimal-ptest-all core-image-sato:do_populate_sdk", "SANITYTARGETS" : "core-image-sato:do_testsdk" } }, @@ -344,7 +344,7 @@ }, "step2" : { "MACHINE" : "qemux86-64", - "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-sato-sdk-ptest core-image-sato:do_populate_sdk", + "BBTARGETS" : "core-image-sato core-image-sato-sdk core-image-minimal core-image-minimal-dev core-image-minimal-ptest-all core-image-sato:do_populate_sdk", "SANITYTARGETS" : "core-image-sato:do_testsdk" }, -- 2.31.1
|
|
Re: hardknott core-image-weston weston is crashing
On 5/26/21 5:02 AM, Marek Belisko wrote:
Hi,there is similar segv I see on master, Can you test this patch on master and see if that works? secondly, also try master branch of weston and see if it fixed it then we can narrow down needed backports ZoranBR,
|
|
OpenEmbedded Happy Hour May 26 8pm/2000 UTC
Denys Dmytriyenko
Hi,
Due to the Yocto Project Summit running during our regular OpenEmbedded Happy Hour today, we decided to move it down by 3 hours and have Happy Hour at the end of the Summit, May 26 @ 2000/8pm UTC (4pm ET / 1pm PT). Please join us and socialize with fellow developers and have some good time. https://www.openembedded.org/wiki/Calendar https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+May+26&iso=20210526T20 -- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
|
|
Re: gstreamer-emements support fdkaacenc/fdkaacdec
#yocto
On 5/26/21 5:01 AM, sateesh m wrote:
Hi Guys, see http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.3.bb?h=dunfell#n114 change that to -Dfdkaac=enabled if it works, then perhaps turn that into packageconfig and send a patch as well if you can --
|
|
[meta-zephyr][PATCH 5/5] zephyr-mqtt-publisher: Add recipe for mqtt publisher
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
This sample application provides an example of using the the MBEDTLS library. Signed-off-by: Amit Kucheria <amit.kucheria.ext@...> --- recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb diff --git a/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb b/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb new file mode 100644 index 000000000000..b4e306742e44 --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb @@ -0,0 +1,5 @@ +include zephyr-sample.inc + +ZEPHYR_SRC_DIR = "${S}/samples/net/mqtt_publisher" + +ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls" -- 2.25.1
|
|
[meta-zephyr][PATCH 4/5] zephyr-websocket-client: Add recipe for websocket client
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
This sample application provides an example of using the the MBEDTLS library. Signed-off-by: Amit Kucheria <amit.kucheria.ext@...> --- recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb diff --git a/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb b/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb new file mode 100644 index 000000000000..428f75e18adb --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb @@ -0,0 +1,5 @@ +include zephyr-sample.inc + +ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/websocket_client" + +ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls" -- 2.25.1
|
|
[meta-zephyr][PATCH 3/5] zephyr-http-client: Add recipe for http client
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
This sample application provides an example of using the the MBEDTLS library. Signed-off-by: Amit Kucheria <amit.kucheria.ext@...> --- recipes-kernel/zephyr-kernel/zephyr-http-client.bb | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-http-client.bb diff --git a/recipes-kernel/zephyr-kernel/zephyr-http-client.bb b/recipes-kernel/zephyr-kernel/zephyr-http-client.bb new file mode 100644 index 000000000000..cf3c322c20ce --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-http-client.bb @@ -0,0 +1,5 @@ +include zephyr-sample.inc + +ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/http_client" + +ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls" -- 2.25.1
|
|
[meta-zephyr][PATCH 2/5] zephyr-echo-client: Add recipe for echo client
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
This sample application provides an example of using the the MBEDTLS library. Signed-off-by: Amit Kucheria <amit.kucheria.ext@...> --- recipes-kernel/zephyr-kernel/zephyr-echo-client.bb | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-echo-client.bb diff --git a/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb b/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb new file mode 100644 index 000000000000..c17e1e78f6b5 --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb @@ -0,0 +1,5 @@ +include zephyr-sample.inc + +ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/echo_client" + +ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls" -- 2.25.1
|
|
[meta-zephyr][PATCH 1/5] zephyr-kernel: Clone mbedtls
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
MBed TLS is a library that implements cryptographic primitives and SSL/TLS and DTLS protocols that are needed in secure network communications. Add it to the kernel include files to build and link against applications that need mbedtls. Signed-off-by: Amit Kucheria <amit.kucheria.ext@...> --- recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 + recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc | 1 + recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 1 + 3 files changed, 3 insertions(+) diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index 330fe59aebe5..c9acbbbc3645 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -28,6 +28,7 @@ ZEPHYR_MODULES = "" ZEPHYR_MODULES_append_arm = "\;${S}/modules/cmsis" ZEPHYR_MODULES_append_nordic = "\;${S}/modules/hal/nordic" ZEPHYR_MODULES_append_stm32 = "\;${S}/modules/hal/stm32" +ZEPHYR_MODULES_append_mbedtls = "\;${S}/modules/lib/mbedtls" ZEPHYR_MODULES_append_openamp = "\;${S}/modules/lib/open-amp\;${S}/modules/hal/libmetal" EXTRA_OECMAKE_append = " -DZEPHYR_MODULES=${ZEPHYR_MODULES}" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc index 6ea15931607d..a0e358ecd4f4 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc @@ -6,5 +6,6 @@ SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df" SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef" SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb" SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0" +SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7" PV = "2.6.0-rc1+git${SRCPV}" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc index 9fc08baaf210..8dcfec6f1f88 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc @@ -17,6 +17,7 @@ SRC_URI = "\ git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \ git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \ git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \ + git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;destsuffix=git/modules/lib/mbedtls;name=mbedtls \ git://github.com/zephyrproject-rtos/open-amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-amp \ git://github.com/zephyrproject-rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal;name=libmetal \ git://github.com/zephyrproject-rtos/tinycrypt.git;protocol=https;destsuffix=git/modules/crypto/tinycrypt;name=tinycrypt \ -- 2.25.1
|
|
[meta-zephyr][PATCH 0/5] Add mbedtls support and sample applications
Amit Kucheria
From: Amit Kucheria <amit.kucheria.ext@...>
MBed TLS is a library that implements cryptographic primitives and SSL/TLS and DTLS protocols that are needed in secure network communications. Add it to the kernel include files to build and link against applications that need mbedtls. Add a few sample applications that utilize mbedtls library too. Amit Kucheria (5): zephyr-kernel: Clone mbedtls zephyr-echo-client: Add recipe for echo client zephyr-http-client: Add recipe for http client zephyr-websocket-client: Add recipe for websocket client zephyr-mqtt-publisher: Add recipe for mqtt publisher recipes-kernel/zephyr-kernel/zephyr-echo-client.bb | 5 +++++ recipes-kernel/zephyr-kernel/zephyr-http-client.bb | 5 +++++ recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 + recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0-rc1.inc | 1 + recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 1 + recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb | 5 +++++ recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb | 5 +++++ 7 files changed, 23 insertions(+) create mode 100644 recipes-kernel/zephyr-kernel/zephyr-echo-client.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-http-client.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb -- 2.25.1
|
|
[meta-mingw][PATCH] zstd: Fix MinGW builds
Joshua Watt
Fixes the MinGW builds for zstd
Signed-off-by: Joshua Watt <JPEWhacker@...> --- recipes-extended/zstd/zstd_%.bbappend | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 recipes-extended/zstd/zstd_%.bbappend diff --git a/recipes-extended/zstd/zstd_%.bbappend b/recipes-extended/zstd/zstd_%.bbappend new file mode 100644 index 0000000..3b2b991 --- /dev/null +++ b/recipes-extended/zstd/zstd_%.bbappend @@ -0,0 +1,2 @@ +EXTRA_OEMAKE_append_mingw32 = " OS=Windows" +FILES_${PN}_append_mingw32 = " ${libdir}/*.dll" -- 2.31.1
|
|
[meta-parsec][PATCH] Correct typo: crago-bitbake
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
--- meta-parsec/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-parsec/README.md b/meta-parsec/README.md index a2736b6..6d938a6 100644 --- a/meta-parsec/README.md +++ b/meta-parsec/README.md @@ -75,7 +75,7 @@ to ensure maximum reproducibility. versions of parsec recipes. https://github.com/meta-rust/cargo-bitbake - When you have crago-bitbake built: + When you have cargo-bitbake built: 1. Checkout the required version of parsec repository. 2. Run cargo-bitbake inside the repository. It will produce a BB file. 3. Create a new include file with SRC_URI and LIC_FILES_CHKSUM from the BB file. -- 2.27.0
|
|
Re: using grpc fails with linker error: file in wrong format
Juergen Landwehr
Hello Khem,
we use CMake as build system. I checked the "sysdig" recipe and they defined both the "grpc" and "grpc-native" (same with protbuf) in the DEPENDS variable like so: DEPENDS += "... grpc grpc-native protobuf protobuf-native ..." If I do this in my recipe I get the following error: which is correct as the directory ".../recipe-sysroot/usr/bin" does not contain any grpc plugins. However the directory ".../recipe-sysroot-native/usr/bin" does (due to the dependency to grpc-native). -- Found Protobuf: /data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/corei7-64-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot/usr/lib/libprotobuf.so;-lpthread (found version "3.12.3") CMake Error at /data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/corei7-64-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot/usr/lib/cmake/grpc/gRPCTargets.cmake:197 (message): The imported target "gRPC::grpc_cpp_plugin" references the file "/data/jenkins/workspace/e0_mbient_yocto_mbient_manifests_master_downstream/build/tmp/work/corei7-64-mbient-linux/tokenmaster-client/git-r0/recipe-sysroot/usr/bin/grpc_cpp_plugin" but this file does not exist. Possible reasons include: It seems to work for sysdig, as they do not use "find_package(Protobuf)" or "find_package("gRPC") to detect gRPC related libraries/programs but use some custom code. So it looks like: 1) If I use "DEPENDS += "... grpc-native protobuf-native ..." I am able to generate grpc stubs and I am also able to successfully build my component, but only, if the build-host and target-host are compatible => NO CROSS COMPING 2) If I use "DEPENDS += "... grpc grpc-native protobuf protobuf-native ..." CMake immediately complains, that some the grpc plugins are missing 3) Using RDEPENDS seems to have no effect So it seems the only way to make this work is to use "DEPENDS += grpc grpc-native ...." and write some custom CMake code to detect grpc related libraries (e.g. libgrpc++.so) and programs (e.g. protoc, grpc_cpp_plugin). But again, I am new to Yocto and still hope, that there is an easier way?
|
|