From: Paul Barker <paul@pbarker.dev>
To: Benhur Tessele <benhur.tessele@est.tech>,
openembedded-core@lists.openembedded.org
Cc: Randy MacLeod <Randy.MacLeod@windriver.com>
Subject: Re: [PATCH 0/2] rust: add rust-analyzer support
Date: Thu, 01 Oct 2026 15:13:21 +0100 [thread overview]
Message-ID: <6ded5087cc73adf490441e55b296d3130da129f6.camel@pbarker.dev> (raw)
In-Reply-To: <20261001125630.760962-1-benhur.tessele@est.tech>
On Thu, 2026-10-01 at 14:56 +0200, Benhur Tessele wrote:
> rust-analyzer is built as part of the Rust tools but was neither
> installed nor packaged. This series packages it and wires it into the
> Rust SDK next to clippy and rustfmt.
>
> Patch 1 adds a rust-tools-analyzer package for the target and nativesdk
> variants. Beyond the frontend binary it also ships the proc-macro server
> and depends on the standard library sources, both of which are required
> for rust-analyzer to actually function.
>
> Patch 2 adds it to the cross-canadian toolchain so that an SDK built with
> SDK_FEATURES = "rust" provides rust-analyzer out of the box.
>
> Testing:
> - Patches validated with patchset.
> - Built an SDK with SDK_FEATURES = "rust", installed it in a container,
> and confirmed rust-analyzer resolves the standard library and expands
> proc-macros end to end: diagnostics/analysis-stats on a crate using a
> derive macro succeed, with the proc-macro server started from
> <sysroot>/libexec.
> - Built core-image-minimal with rust-tools-analyzer installed, booted it
> under qemu, and confirmed the rust-analyzer frontend and the
> rust-analyzer-proc-macro-srv binary are present with their libraries
> resolving.
>
> Benhur Tessele (2):
> rust: package rust-analyzer as rust-tools-analyzer
> packagegroup-rust-cross-canadian: add rust-analyzer to the SDK
Hi,
Two quick questions here:
1) What's the intended use case for rust-analyzer, particularly on the
target? I think we need at least a brief reason why it's worth
enabling this.
2) What impact does this have on the build and package creation time for
rust?
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-10-01 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 12:56 [PATCH 0/2] rust: add rust-analyzer support Benhur Tessele
2026-10-01 12:56 ` [PATCH 1/2] rust: package rust-analyzer as rust-tools-analyzer Benhur Tessele
2026-10-01 12:56 ` [PATCH 2/2] packagegroup-rust-cross-canadian: add rust-analyzer to the SDK Benhur Tessele
2026-10-01 14:08 ` [OE-core] [PATCH 0/2] rust: add rust-analyzer support Mathieu Dubois-Briand
2026-10-02 9:05 ` Paul Barker
2026-10-02 14:54 ` Benhur T
2026-10-01 14:13 ` Paul Barker [this message]
2026-10-01 15:47 ` Benhur T
2026-10-02 9:00 ` Paul Barker
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=6ded5087cc73adf490441e55b296d3130da129f6.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Randy.MacLeod@windriver.com \
--cc=benhur.tessele@est.tech \
--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