From: Fiona Behrens <me@kloenk.dev>
To: Tamir Duberstein <tamird@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Boris-Chengbiao Zhou" <bobo1239@web.de>,
"Kees Cook" <kees@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lukas Wirth" <lukas.wirth@ferrous-systems.com>
Subject: Re: [PATCH v2 6/7] scripts: generate_rust_analyzer.py: identify crates explicitly
Date: Wed, 12 Mar 2025 20:07:19 +0100 [thread overview]
Message-ID: <m2bju6ysns.fsf@kloenk.dev> (raw)
In-Reply-To: <20250311-rust-analyzer-host-v2-6-30220e116511@gmail.com> (Tamir Duberstein's message of "Tue, 11 Mar 2025 21:17:27 -0400")
Tamir Duberstein <tamird@gmail.com> writes:
> Use the return of `append_crate` to declare dependency on that crate.
> This allows multiple crates with the same display_name be defined, which
> we'll use to define host crates separately from target crates.
>
> Signed-off-by: Tamir Duberstein <tamird@gmail.com>
Reviewed-by: Fiona Behrens <me@kloenk.dev>
> ---
> scripts/generate_rust_analyzer.py | 60 +++++++++++++++++++--------------------
> 1 file changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/scripts/generate_rust_analyzer.py b/scripts/generate_rust_analyzer.py
> index 1bb185ae2e87..e1002867735b 100755
> --- a/scripts/generate_rust_analyzer.py
> +++ b/scripts/generate_rust_analyzer.py
> @@ -68,40 +68,38 @@ def generate_crates(
> line = line.replace("\n", "")
> cfg.append(line)
>
> - # Now fill the crates list -- dependencies need to come first.
> - #
> - # Avoid O(n^2) iterations by keeping a map of indexes.
> + # Now fill the crates list.
> crates: list[Crate] = []
> - crates_indexes: dict[str, int] = {}
> crates_cfgs = args_crates_cfgs(cfgs)
>
> def append_crate(
> display_name: str,
> root_module: pathlib.Path,
> - deps: list[str],
> + deps: list[Dependency],
> cfg: list[str] = [],
> is_workspace_member: bool = True,
> - ) -> None:
> - crates_indexes[display_name] = len(crates)
> + ) -> Dependency:
> + index = len(crates)
> crates.append({
> "display_name": display_name,
> "root_module": str(root_module),
> "is_workspace_member": is_workspace_member,
> - "deps": [{"crate": crates_indexes[dep], "name": dep} for dep in deps],
> + "deps": deps,
> "cfg": cfg,
> "edition": "2021",
> "env": {
> "RUST_MODFILE": "This is only for rust-analyzer"
> },
> })
> + return {"crate": index, "name": display_name}
>
> def append_proc_macro_crate(
> display_name: str,
> root_module: pathlib.Path,
> - deps: list[str],
> + deps: list[Dependency],
> cfg: list[str] = [],
> - ) -> None:
> - append_crate(display_name, root_module, deps, cfg)
> + ) -> Dependency:
> + dep = append_crate(display_name, root_module, deps, cfg)
> proc_macro_dylib_name = subprocess.check_output(
> [os.environ["RUSTC"], "--print", "file-names", "--crate-name", display_name, "--crate-type", "proc-macro", "-"],
> stdin=subprocess.DEVNULL,
> @@ -112,13 +110,14 @@ def generate_crates(
> "proc_macro_dylib_path": str(objtree / "rust" / proc_macro_dylib_name),
> }
> crates[-1] = crate
> + return dep
>
> def append_sysroot_crate(
> display_name: str,
> - deps: list[str],
> + deps: list[Dependency],
> cfg: list[str] = [],
> - ) -> None:
> - append_crate(
> + ) -> Dependency:
> + return append_crate(
> display_name,
> sysroot_src / display_name / "src" / "lib.rs",
> deps,
> @@ -129,34 +128,34 @@ def generate_crates(
> # NB: sysroot crates reexport items from one another so setting up our transitive dependencies
> # here is important for ensuring that rust-analyzer can resolve symbols. The sources of truth
> # for this dependency graph are `(sysroot_src / crate / "Cargo.toml" for crate in crates)`.
> - append_sysroot_crate("core", [], cfg=crates_cfgs.get("core", []))
> - append_sysroot_crate("alloc", ["core"])
> - append_sysroot_crate("std", ["alloc", "core"])
> - append_sysroot_crate("proc_macro", ["core", "std"])
> + core = append_sysroot_crate("core", [], cfg=crates_cfgs.get("core", []))
> + alloc = append_sysroot_crate("alloc", [core])
> + std = append_sysroot_crate("std", [alloc, core])
> + proc_macro = append_sysroot_crate("proc_macro", [core, std])
>
> - append_crate(
> + compiler_builtins = append_crate(
> "compiler_builtins",
> srctree / "rust" / "compiler_builtins.rs",
> [],
> )
>
> - append_proc_macro_crate(
> + macros = append_proc_macro_crate(
> "macros",
> srctree / "rust" / "macros" / "lib.rs",
> - ["std", "proc_macro"],
> + [std, proc_macro],
> )
>
> - append_crate(
> + build_error = append_crate(
> "build_error",
> srctree / "rust" / "build_error.rs",
> - ["core", "compiler_builtins"],
> + [core, compiler_builtins],
> )
>
> def append_crate_with_generated(
> display_name: str,
> - deps: list[str],
> - ) -> None:
> - append_crate(
> + deps: list[Dependency],
> + ) -> Dependency:
> + dep = append_crate(
> display_name,
> srctree / "rust" / display_name / "lib.rs",
> deps,
> @@ -174,10 +173,11 @@ def generate_crates(
> }
> }
> crates[-1] = crate
> + return dep
>
> - append_crate_with_generated("bindings", ["core"])
> - append_crate_with_generated("uapi", ["core"])
> - append_crate_with_generated("kernel", ["core", "macros", "build_error", "bindings", "uapi"])
> + bindings = append_crate_with_generated("bindings", [core])
> + uapi = append_crate_with_generated("uapi", [core])
> + kernel = append_crate_with_generated("kernel", [bindings, build_error, core, macros, uapi])
>
> def is_root_crate(build_file: pathlib.Path, target: str) -> bool:
> try:
> @@ -207,7 +207,7 @@ def generate_crates(
> append_crate(
> name,
> path,
> - ["core", "kernel"],
> + [core, kernel],
> cfg=cfg,
> )
next prev parent reply other threads:[~2025-03-12 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 1:17 [PATCH v2 0/7] rust: generate_rust_analyzer.py: define host crates Tamir Duberstein
2025-03-12 1:17 ` [PATCH v2 1/7] scripts: generate_rust_analyzer.py: add missing whitespace Tamir Duberstein
2025-03-12 19:00 ` Fiona Behrens
2025-03-12 1:17 ` [PATCH v2 2/7] scripts: generate_rust_analyzer.py: use double quotes Tamir Duberstein
2025-03-12 19:01 ` Fiona Behrens
2025-03-12 1:17 ` [PATCH v2 3/7] scripts: generate_rust_analyzer.py: add trailing comma Tamir Duberstein
2025-03-12 19:02 ` Fiona Behrens
2025-03-12 1:17 ` [PATCH v2 4/7] scripts: generate_rust_analyzer.py: add type hints Tamir Duberstein
2025-03-15 12:20 ` Tamir Duberstein
2025-03-19 21:25 ` Trevor Gross
2025-03-19 22:25 ` Tamir Duberstein
2025-03-12 1:17 ` [PATCH v2 5/7] scripts: generate_rust_analyzer.py: use str(pathlib.Path) Tamir Duberstein
2025-03-12 19:04 ` Fiona Behrens
2025-03-12 1:17 ` [PATCH v2 6/7] scripts: generate_rust_analyzer.py: identify crates explicitly Tamir Duberstein
2025-03-12 19:07 ` Fiona Behrens [this message]
2025-03-12 1:17 ` [PATCH v2 7/7] scripts: generate_rust_analyzer.py: define host crates Tamir Duberstein
2025-03-12 19:09 ` Fiona Behrens
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=m2bju6ysns.fsf@kloenk.dev \
--to=me@kloenk.dev \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=bobo1239@web.de \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.wirth@ferrous-systems.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
/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