Google Git
Sign in
fuchsia/sdk-samples/drivers/1ad56b4d923fc308d242d382ff9c60faedce6399
commit
1ad56b4d923fc308d242d382ff9c60faedce6399
[log]
author
Abseil Team <absl-team@fuchsia.infra.roller.google.com>
Wed Jan 07 14:58:43 2026 -0800
committer
CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Wed Jan 07 14:58:43 2026 -0800
tree
836349121e59225186d843c9daa6e819981dc35b
parent
10a2a18b19be227d116b7f552cb080155c62c60c [diff]
[roll] Roll third_party/googletest Separate the creation of the Premature Exit File from supporting Death Tests.

The [Premature Exit File](https://google.github.io/googletest/advanced.html#detecting-test-premature-exit)
can be used for more than just death tests. Runners can use it to detect any
kind of unexpected exit.

Presently, its creation is tied to whether a platform supports Death
Tests. This change removes that coupling (though if Death Tests are supported,
then the Premature Exit file is implicitly supported).

PiperOrigin-RevId: 853416224
Original-Revision: 5554fcaab40f8814e6e277a56175683405f0cdd5

Roller-URL: https://cr-buildbucket.appspot.com/build/8693294209293523713
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9ddd23250b7182a0f7042d7b46168722dc79baec
Reviewed-on: https://fuchsia-review.googlesource.com/c/sdk-samples/drivers/+/1469205
Commit-Queue: GI Roller <global-integration-roller@fuchsia-infra.iam.gserviceaccount.com>
1 file changed
tree: 836349121e59225186d843c9daa6e819981dc35b
  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. MODULE.bazel
  18. MODULE.bazel.lock
  19. OWNERS
  20. PATENTS
  21. README.md
  22. rollers.textproto
  23. shac.star
  24. shac.textproto
  25. WORKSPACE.bzlmod
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.