From: Zhihang Wei <wzh@ilbers.de>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/3] Add helper and documentation for rust packaging
Date: Wed, 13 May 2026 17:16:33 +0200 [thread overview]
Message-ID: <39231b8b-dc95-4288-87eb-013d3bca4048@ilbers.de> (raw)
In-Reply-To: <20260416152238.1651692-1-Quirin.Gylstorff@siemens.com>
Applied to next, removed some trailing empty lines at EOF. Thanks.
Zhihang
On 4/16/26 17:22, 'Quirin Gylstorff' via isar-users wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> This adds based on https://rust-team.pages.debian.net/book/ some
> documentation add a generator to package rust crates.
>
> The generator is the same as used by Debian but we don't use the
> approach from debcargo-conf as `debcargo cargo` executes the following
> steps add once:
> - fetch source
> - generate orig tarball
> - generate debian folder
>
> As this is not compatible with the concepts of bitbake recipes we use
> the http fetcher and the by `debcargo` generated debian folder. This
> approach is intended to build crates stored in a registry(e.g. crates.io).
>
> The crates package generated by this script should be package upstream
> to avoid maintaining them forever.
>
> Crates not in a registry need to manually packaged.
> Changes v3:
> - rebase onto next
> - use crate instead of https fetcher
> - some script cleanups
>
> Changes v2:
> - add MIT-0 license to generated rust recipes
> - use BPN instead of PN in rust-hello-isar
> - add line for cargo-debstatus to check already packaged dpendencies
>
> Quirin Gylstorff (3):
> Add script to generate a recipe for cargo.io crates
> Add example of a rust hello world as isar recipe
> user_manual: add rust section
>
> doc/user_manual.md | 68 ++++++++++++++
> .../recipes-app/rust-hello-isar/files/rules | 27 ++++++
> .../files/rust-hello-isar/Cargo.toml | 6 ++
> .../files/rust-hello-isar/src/main.rs | 3 +
> .../rust-hello-isar/rust-hello-isar_0.1.bb | 22 +++++
> scripts/generate_cargo_crate.sh | 92 +++++++++++++++++++
> 6 files changed, 218 insertions(+)
> create mode 100755 meta-isar/recipes-app/rust-hello-isar/files/rules
> create mode 100644 meta-isar/recipes-app/rust-hello-isar/files/rust-hello-isar/Cargo.toml
> create mode 100644 meta-isar/recipes-app/rust-hello-isar/files/rust-hello-isar/src/main.rs
> create mode 100644 meta-isar/recipes-app/rust-hello-isar/rust-hello-isar_0.1.bb
> create mode 100755 scripts/generate_cargo_crate.sh
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/39231b8b-dc95-4288-87eb-013d3bca4048%40ilbers.de.
prev parent reply other threads:[~2026-05-13 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 15:22 'Quirin Gylstorff' via isar-users
2026-04-16 15:22 ` [PATCH v3 1/3] Add script to generate a recipe for cargo.io crates 'Quirin Gylstorff' via isar-users
2026-04-16 15:22 ` [PATCH v3 2/3] Add example of a rust hello world as isar recipe 'Quirin Gylstorff' via isar-users
2026-04-16 15:22 ` [PATCH v3 3/3] user_manual: add rust section 'Quirin Gylstorff' via isar-users
2026-05-13 15:16 ` Zhihang Wei [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=39231b8b-dc95-4288-87eb-013d3bca4048@ilbers.de \
--to=wzh@ilbers.de \
--cc=Quirin.Gylstorff@siemens.com \
--cc=isar-users@googlegroups.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