| commit | be836ab47c73ff0ab2ceb8f0df862053b88a935d | [log] [tgz] |
|---|---|---|
| author | Shuhei Takahashi <nya@chromium.org> | Fri Apr 28 00:07:09 2023 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 28 01:17:09 2023 |
| tree | 6f66fcb3e8e7467d4b27bee6eb8258c96ff373a6 | |
| parent | 048f9a0684fa373f2f2df5fb79b1f6a9ad902d91 [diff] |
Revert "Update prebuilts for the new snapshot" This reverts commit 048f9a0684fa373f2f2df5fb79b1f6a9ad902d91. Reason for revert: I thought the file was stale but it is up to date thanks to crrev.com/c/4453890 Original change's description: > Update prebuilts for the new snapshot > > BUG=b:262460834 > TEST=BOARD=amd64-generic bazel build --config=prebuilts/amd64-generic \ > //bazel/images:chromiumos_base_image > > Change-Id: I8af78eb1ab43129f16db8c813e35cdac199c20ed > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/4480558 > Auto-Submit: Shuhei Takahashi <nya@chromium.org> > Tested-by: Shuhei Takahashi <nya@chromium.org> > Commit-Queue: Shuhei Takahashi <nya@chromium.org> > Commit-Queue: Matt Stark <msta@google.com> > Reviewed-by: Matt Stark <msta@google.com> Bug: b:262460834 Change-Id: Ie0864a41b12206303033795714be2d8edf6a658f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/4485917 Reviewed-by: Matt Stark <msta@google.com> Commit-Queue: Shuhei Takahashi <nya@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
This repository provides common rules and configuration for Bazel projects in Chrome OS.
The code is this directory is experimental and under active development. Stability and functionality is not guaranteed :)
We use rust_analyzer to generate a rust-project.json file in the workspace root, which allows vscode to understand your dependencies.
Simply install the rust_analyzer VSCode plugin, and then add the following to your .vscode/tasks.json file, substituting TARGET for a label of any bazel target you want to depend on. VSCode will then analyze all the transitive dependencies of the specified targets.
For example, I might use the following line:
"args": ["run", "//rules_cros/toolchains/rust:gen_rust_project", "--", "//rules_cros/toolchains/rust/examples/use_local_crate/...", "//rules_cros/toolchains/rust/examples/hello_world:helllo_world"],
{ "version": "2.0.0", "tasks": [ { "label": "Generate rust-project.json", "command": "bazel", "args": ["run", "//rules_cros/toolchains/rust:gen_rust_project", "--", "<TARGET1>", "<TARGET2>", "..."], "options": { "cwd": "${workspaceFolder}" }, "group": "build", "problemMatcher": [], "presentation": { "reveal": "never", "panel": "dedicated", }, "runOptions": { "runOn": "folderOpen" } }, ] }
If you add a new file, you may need to manually re-run the task.