Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Benhur T <benhur.tessele@est.tech>
To: Paul Barker <paul@pbarker.dev>, openembedded-core@lists.openembedded.org
Cc: Randy MacLeod <Randy.MacLeod@windriver.com>
Subject: Re: [PATCH 0/2] rust: add rust-analyzer support
Date: Thu, 1 Oct 2026 17:47:48 +0200	[thread overview]
Message-ID: <693a4702-0920-4cb2-8669-1aae65b5e07d@est.tech> (raw)
In-Reply-To: <6ded5087cc73adf490441e55b296d3130da129f6.camel@pbarker.dev>

> 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?
Hi Paul, thanks for the relevant comments.

1) Short answer: I don't know. I agree with you seems odd, but I just 
followed what's already done for the other tools (clippy, rustfmt). I'm 
more than happy to remove it from target is that's the right approach.

2) On my build environment (poky/qemux86-64) there's a build time increase.

master
|- do_install: Elapsed time: 524.36 seconds
`- do_package: Elapsed time: 16.49 seconds

with my patches
|- do_install: Elapsed time: 619.82 seconds
`- do_package: Elapsed time: 17.16 seconds

Best regards,
Ben


  reply	other threads:[~2026-10-01 15:48 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
2026-10-01 15:47   ` Benhur T [this message]
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=693a4702-0920-4cb2-8669-1aae65b5e07d@est.tech \
    --to=benhur.tessele@est.tech \
    --cc=Randy.MacLeod@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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