Google Git
Sign in
fuchsia/sdk-samples/drivers/126cfaf4baa07e61d4782b7337bb66ea1cf88bd0
commit
126cfaf4baa07e61d4782b7337bb66ea1cf88bd0
[log]
author
Abseil Team <absl-team@fuchsia.infra.roller.fuchsia.infra.roller.google.com>
Fri Jun 13 09:33:40 2025 -0700
committer
CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Jun 13 09:33:40 2025 -0700
tree
75a6ddc3e33421183e009e928998af95349c0559
parent
208b5c850bd152b6f7a55e9d9c87d592676188a2 [diff]
[roll] Roll third_party/fuchsia-infra-bazel-rules [roll] Roll third_party/googletest Although the following paragraph explains there is a better solution, having this technique in the bullet point seems to suggest that this technique is considered as a valid alternative. It would be better to drop it or make it clear that this technique is not recommended.

PiperOrigin-RevId: 771116391
Original-Revision: 35b75a2cba6ef72b7ce2b6b94b05c54ca07df866

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia-infra-bazel-rules/+/1300564
Original-Revision: 498237fba447720386a8cea9f8931aa976d5e089

Roller-URL: https://cr-buildbucket.appspot.com/build/8712161908921823441
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3650c94028e13a17ffcfcacc5eba6de0cafce1ef
Reviewed-on: https://fuchsia-review.googlesource.com/c/sdk-samples/drivers/+/1300567
Commit-Queue: GI Roller <global-integration-roller@fuchsia-infra.iam.gserviceaccount.com>
1 file changed
tree: 75a6ddc3e33421183e009e928998af95349c0559
  1. manifests/
  2. scripts/
  3. src/
  4. third_party/
  5. tools/
  6. platform_mappings ⇨ third_party/fuchsia-infra-bazel-rules/config/fuchsia_platform_mappings
  7. .bazelrc
  8. .clang-format
  9. .gitignore
  10. .gitmodules
  11. AUTHORS
  12. BUILD.bazel
  13. CONTRIBUTING.md
  14. driver-samples.code-workspace
  15. fuchsia_env.toml
  16. LICENSE
  17. OWNERS
  18. PATENTS
  19. README.md
  20. rollers.textproto
  21. shac.star
  22. shac.textproto
  23. WORKSPACE.bazel
README.md

Fuchsia samples using the Fuchsia SDK

This repository contains instructions and source code to build, package and run Fuchsia samples using only the Fuchsia SDK.

Set up and bootstrap the SDK driver samples repository

Clone this SDK driver samples repository on your host machine. This repository contains sample driver components and the Bazel-based Fuchsia SDK.

The tasks include:

  • Bootstrap the SDK driver samples repository.
  • Download the SDK toolchain to initialize the SDK environment.
  • Verify that you can run ffx commands.

Do the following:

  1. Open a terminal.

  2. In the terminal, change to your home directory:

    cd

  3. Clone the SDK driver samples repository:

    git clone https://fuchsia.googlesource.com/sdk-samples/drivers fuchsia-drivers --recurse-submodules

    This git clone command creates a new directory named fuchsia-drivers and clones the content of the SDK driver samples repository{:.external}.

  4. Go to the new directory:

    cd fuchsia-drivers

  5. Run the bootstrap script to install Bazel and other required dependencies:

    scripts/bootstrap.sh

  6. Download the SDK toolchain:

    tools/bazel build @fuchsia_sdk//:fuchsia_toolchain_sdk

    The first build may take a few minutes to download dependencies, such as Clang and Fuchsia IDK (which includes the ffx tool).

    When finished successfully, it prints output similar to the following:

    $ tools/bazel build @fuchsia_sdk//:fuchsia_toolchain_sdk
...
INFO: Elapsed time: 23.608s, Critical Path: 0.03s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action

  7. To verify that you can use the ffx tool in your environment, run the following command:

    tools/ffx sdk version

    This command prints output similar to the following:

    $ tools/ffx sdk version
14.20230811.2.1

    At this point, you only need to confirm that you can run ffx commands without error.

    Note: The output above shows the version 14.20230811.2.1, which indicates that this SDK was built and published on August 11, 2023.