Google Git
Sign in
cos / mirrors / cros / chromiumos / platform / rules_cros / 048f9a0684fa373f2f2df5fb79b1f6a9ad902d91
commit048f9a0684fa373f2f2df5fb79b1f6a9ad902d91[log] [tgz]
authorShuhei Takahashi <nya@chromium.org>Thu Apr 27 13:27:06 2023 +0900
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 27 05:49:23 2023 +0000
tree35484d257c7f4f6615e260a49441bcfcfc0f2fe6
parent010683bdd3de7494538e9b489482f56c8487cca8 [diff]
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>
1 file changed
tree: 35484d257c7f4f6615e260a49441bcfcfc0f2fe6
  1. bazelrcs/
  2. cros/
  3. platforms/
  4. test/
  5. third_party/
  6. toolchains/
  7. workspace_root/
  8. .bazelrc
  9. .gitignore
  10. common.bazelrc
  11. DIR_METADATA
  12. LICENSE
  13. OWNERS
  14. OWNERS.clover
  15. README.md
  16. run_tests.sh
  17. WORKSPACE.cros
README.md

Chrome OS Bazel Rules

Overview

This repository provides common rules and configuration for Bazel projects in Chrome OS.

Documentation

The code is this directory is experimental and under active development. Stability and functionality is not guaranteed :)

Configuring dev experience

Rust

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.