From: Deepesh.Varatharajan@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com, Deepesh.Varatharajan@windriver.com
Subject: [PATCH] cargo-c: Move recipe out of rust directory
Date: Fri, 6 Mar 2026 00:24:28 -0800 [thread overview]
Message-ID: <20260306082428.203033-1-Deepesh.Varatharajan@windriver.com> (raw)
From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
cargo-c is an external Cargo extension used to build Rust libraries
with a C-compatible ABI and generate C headers and pkg-config files.
Since it is not part of the standard Rust toolchain, move it from the
rust directory to cargo-c under recipes-devtools for better organization
and maintainability.
Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
---
meta/recipes-devtools/{rust => cargo-c}/cargo-c-crates.inc | 0
.../0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch | 0
.../{rust => cargo-c}/cargo-c_0.10.20+cargo-0.94.0.bb | 0
3 files changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-devtools/{rust => cargo-c}/cargo-c-crates.inc (100%)
rename meta/recipes-devtools/{rust => cargo-c}/cargo-c/0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch (100%)
rename meta/recipes-devtools/{rust => cargo-c}/cargo-c_0.10.20+cargo-0.94.0.bb (100%)
diff --git a/meta/recipes-devtools/rust/cargo-c-crates.inc b/meta/recipes-devtools/cargo-c/cargo-c-crates.inc
similarity index 100%
rename from meta/recipes-devtools/rust/cargo-c-crates.inc
rename to meta/recipes-devtools/cargo-c/cargo-c-crates.inc
diff --git a/meta/recipes-devtools/rust/cargo-c/0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch b/meta/recipes-devtools/cargo-c/cargo-c/0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch
similarity index 100%
rename from meta/recipes-devtools/rust/cargo-c/0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch
rename to meta/recipes-devtools/cargo-c/cargo-c/0001-parking-lot-Use-libc-SYS_futex_time64-on-riscv32.patch
diff --git a/meta/recipes-devtools/rust/cargo-c_0.10.20+cargo-0.94.0.bb b/meta/recipes-devtools/cargo-c/cargo-c_0.10.20+cargo-0.94.0.bb
similarity index 100%
rename from meta/recipes-devtools/rust/cargo-c_0.10.20+cargo-0.94.0.bb
rename to meta/recipes-devtools/cargo-c/cargo-c_0.10.20+cargo-0.94.0.bb
--
2.49.0
reply other threads:[~2026-03-06 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260306082428.203033-1-Deepesh.Varatharajan@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Sundeep.Kokkonda@windriver.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