From: "Anton Antonov" <anton.antonov@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] cargo.bbclass: allow to avoid appending PACKAGECONFIG_CONFARGS
Date: Fri, 16 May 2025 08:07:26 -0700 [thread overview]
Message-ID: <13420.1747408046210278509@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj-0xoyMB9dujwM8O547Bx8OF+gTz_+rrE-brWG+F8Tjxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Hello,
This change also breaks recipes where cargo is used as the top build system but PACKAGECONFIG_CONFARGS should not be included into cargo parameters. See, for example:
https://git.yoctoproject.org/meta-security/tree/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.4.1.bb
What is the reason for this change? If a recipe needs to use PACKAGECONFIG for cargo parameters then the recipe can update CARGO_BUILD_FLAGS accordingly.
With this change I don't have an option to not include PACKAGECONFIG_CONFARGS into parameters. Can it be reverted?
Anton
[-- Attachment #2: Type: text/html, Size: 809 bytes --]
next prev parent reply other threads:[~2025-05-16 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 16:55 [PATCH 1/2] cargo.bbclass: show PACKAGECONFIG_CONFARGS in bbnote martin.jansa
2025-03-20 16:55 ` [PATCH 2/2] cargo.bbclass: allow to avoid appending PACKAGECONFIG_CONFARGS martin.jansa
[not found] ` <182E912DEB60EF95.20788@lists.openembedded.org>
2025-03-20 16:59 ` [OE-core] " Martin Jansa
2025-03-20 17:06 ` Richard Purdie
[not found] ` <182E91CCE4A2B275.19116@lists.openembedded.org>
2025-03-20 17:16 ` Richard Purdie
2025-03-20 17:36 ` Martin Jansa
2025-03-20 17:51 ` Jean-Pierre Geslin
2025-03-20 18:11 ` [OE-core] " Jean-Pierre Geslin
2025-03-24 18:55 ` Alexander Kanavin
2025-03-24 19:30 ` Martin Jansa
2025-03-24 22:29 ` Richard Purdie
2025-03-31 16:18 ` akuster808
2025-03-31 16:28 ` Alexander Kanavin
2025-05-16 15:07 ` Anton Antonov [this message]
2025-05-16 15:55 ` Alexander Kanavin
2025-05-16 16:39 ` Anton Antonov
2025-05-16 17:19 ` [OE-core] " Alexander Kanavin
2025-05-16 17:43 ` Marko, Peter
2025-05-16 17:47 ` Anton Antonov
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=13420.1747408046210278509@lists.openembedded.org \
--to=anton.antonov@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.