Google Git
Sign in
chromium / chromiumos / platform / rules_cros / 5293edfe416ead42dc940651db4280d92aa04af7
commit5293edfe416ead42dc940651db4280d92aa04af7[log] [tgz]
authorRaul E Rangel <rrangel@chromium.org>Fri Apr 21 16:58:56 2023
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 24 06:18:30 2023
tree043a243a96cf6d8185e5c395617b379ca4cb7a39
parentabb18688cec6d95fd4307bc0595cb1c81197ec48 [diff]
bazelrcs/prebuilts: Update prebuilts for stabilize-15429.B

We no longer need chromeos-fonts for amd64!

BUG=b:262460834
TEST=BOARD=amd64-generic bazel build -k --config=prebuilts/amd64-generic  --//bazel/sdk:new-sdk @portage//virtual/target-os-test:all

Change-Id: I2f8ead7af9054881ef8cf22c125a3177d98eb747
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/4453890
Commit-Queue: Shuhei Takahashi <nya@chromium.org>
Tested-by: Raul Rangel <rrangel@chromium.org>
Reviewed-by: Shuhei Takahashi <nya@chromium.org>
Auto-Submit: Raul Rangel <rrangel@chromium.org>
1 file changed
tree: 043a243a96cf6d8185e5c395617b379ca4cb7a39
  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.