All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: yocto@lists.yoctoproject.org, sandro.anders@carmedialab.com
Subject: Re: [yocto] cargo/rust from meta-rust-bin in eSDK of yocto 4.x
Date: Tue, 29 Oct 2024 09:21:16 +0100	[thread overview]
Message-ID: <6f307e84-1224-4a95-becb-18755fcf8e0e@gmail.com> (raw)
In-Reply-To: <PS09.1730138169422773566.enR7@lists.yoctoproject.org>

When working with non-standard Rust versions from whatever other layers, 
I found it makes my life easier when I add the not-used recipes to 
BBMASK from oe-core, something like

BBMASK += "poky/meta/recipes-devtools/rust"

If there is anything that depends on it explicitly, it should fail 
loudly during next build, so it can be fixed. Otherwise bitbake will 
ignore these recipes completely, so it shouldn't clash with the new ones.


  reply	other threads:[~2024-10-29  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 17:56 cargo/rust from meta-rust-bin in eSDK of yocto 4.x sandro.anders
2024-10-29  8:21 ` Gyorgy Sarvari [this message]
2024-10-30  7:52   ` [yocto] " sandro.anders
2025-04-15 11:32     ` Yash Shinde
2025-04-15 11:48       ` sandro.anders

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=6f307e84-1224-4a95-becb-18755fcf8e0e@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=sandro.anders@carmedialab.com \
    --cc=yocto@lists.yoctoproject.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.