From: "Clément Péron" <peron.clem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: "Clément Péron" <peron.clem@gmail.com>
Subject: [RFC PATCH 1/4] jsoncpp: extend with nativesdk
Date: Thu, 20 Jul 2023 18:22:59 +0200 [thread overview]
Message-ID: <20230720162535.116519-2-peron.clem@gmail.com> (raw)
In-Reply-To: <20230720162535.116519-1-peron.clem@gmail.com>
Jsoncpp doesn't extend for the moment with nativesdk
We will need jsoncpp in the next protobuf bump that will require
that.
Add the nativesdk to BBEXTENDS of the jsoncpp recipe.
Signed-off-by: Clément Péron <peron.clem@gmail.com>
---
meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb b/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb
index c54dc9466..086615649 100644
--- a/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb
+++ b/meta-oe/recipes-devtools/jsoncpp/jsoncpp_1.9.5.bb
@@ -22,4 +22,4 @@ inherit cmake
EXTRA_OECMAKE += "-DBUILD_SHARED_LIBS=ON -DBUILD_OBJECT_LIBS=OFF -DJSONCPP_WITH_TESTS=OFF"
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
--
2.41.0
next prev parent reply other threads:[~2023-07-20 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 16:22 [RFC PATCH 0/4] Bump Protobuf/gRPC Clément Péron
2023-07-20 16:22 ` Clément Péron [this message]
2023-07-20 16:23 ` [RFC PATCH 2/4] devtools: protobuf: add utf8-range recipe Clément Péron
2023-07-20 16:23 ` [RFC PATCH 3/4] protobuf: bump to 3.23.4 Clément Péron
2023-07-20 16:23 ` [RFC PATCH 4/4] devtools: grpc: bump to 1.56.2 Clément Péron
2023-07-20 16:38 ` [OE-core] [RFC PATCH 0/4] Bump Protobuf/gRPC Martin Jansa
2023-07-21 9:07 ` Clément Péron
[not found] ` <1773D6CEC3F30D4C.21241@lists.openembedded.org>
2023-07-22 10:11 ` Clément Péron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230720162535.116519-2-peron.clem@gmail.com \
--to=peron.clem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox