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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247038): https://lists.openembedded.org/g/openembedded-core/message/247038 Mute This Topic: https://lists.openembedded.org/mt/121527283/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
