From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"steve@sakoman.com" <steve@sakoman.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap 18/18] rust: Add new varaible RUST_ENABLE_EXTRA_TOOLS
Date: Mon, 05 Aug 2024 10:02:31 +0100 [thread overview]
Message-ID: <beae104500728cbeeba6b3a3c7f7a21477bd5f92.camel@linuxfoundation.org> (raw)
In-Reply-To: <AS1PR10MB56972C3696EF9F76596EABD7FDBE2@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Mon, 2024-08-05 at 08:47 +0000, Marko, Peter wrote:
> -----Original Message-----
> From:
> openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org
> > On Behalf Of Richard Purdie via lists.openembedded.org
> Sent: Sunday, August 4, 2024 23:33
> To: steve@sakoman.com; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][scarthgap 18/18] rust: Add new varaible
> RUST_ENABLE_EXTRA_TOOLS
>
> > On Sun, 2024-08-04 at 10:09 -0700, Steve Sakoman via
> > lists.openembedded.org wrote:
> > > From: Ranjitsinh Rathod <ranjitsinh.rathod@kpit.com>
> > >
> > > There is a need to enable some extra tools from the rust for the
> > > build
> > > and so this new variable will help for that
> > >
> > > This varaible then we can use during do_configure task to add
> > > overall
> > > values as per json format in build -> tools
> > >
> > > Signed-off-by: Ranjitsinh Rathod <ranjitsinh.rathod@kpit.com>
> > > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > > ---
> > > meta/recipes-devtools/rust/rust_1.75.0.bb | 6 +++++-
> > > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > Not sure this is on master?
> >
> > Cheers,
> >
> > Richard
>
> This was already explained here:
> https://lists.openembedded.org/g/openembedded-core/message/202732
Fair enough, thanks!
Cheers,
Richard
prev parent reply other threads:[~2024-08-05 9:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 17:09 [OE-core][scarthgap 00/18] Patch review Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 01/18] libstd-rs,rust-cross-canadian: set CVE_PRODUCT to rust Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 02/18] busybox: CVE-2023-42364 and CVE-2023-42365 fixes Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 03/18] busybox: Add fix for CVE-2023-42366 Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 04/18] libyaml: Fix warning regarding unpatched CVE Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 05/18] qemu: upgrade 8.2.2 -> 8.2.3 Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 06/18] package.py: Fix static debuginfo split Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 07/18] package.py: Fix static library processing Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 08/18] selftest-hardlink: Add additional test cases Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 09/18] create-spdx-*: Support multilibs via SPDX_MULTILIB_SSTATE_ARCHS Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 10/18] create-spdx-3.0/populate_sdk_base: Add SDK_CLASSES inherit mechanism to fix tarball SPDX manifests Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 11/18] oeqa sdk cases: Skip SDK test cases when TCLIBC is newlib Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 12/18] pseudo: Fix to work with glibc 2.40 Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 13/18] pseudo: Update to include open symlink handling bugfix Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 14/18] iptables: fix memory corruption when parsing nft rules Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 15/18] gpgme: move gpgme-tool to own sub-package Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 16/18] rt-tests: rt_bmark.py: fix TypeError Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 17/18] watchdog: Set watchdog_module in default config Steve Sakoman
2024-08-04 17:09 ` [OE-core][scarthgap 18/18] rust: Add new varaible RUST_ENABLE_EXTRA_TOOLS Steve Sakoman
2024-08-04 21:32 ` Richard Purdie
2024-08-05 8:47 ` Marko, Peter
2024-08-05 9:02 ` Richard Purdie [this message]
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=beae104500728cbeeba6b3a3c7f7a21477bd5f92.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Peter.Marko@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
/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