| commit | fac868eb33cabe7f796ab835cee99becb2b1460d | [log] [tgz] |
|---|---|---|
| author | Darren Chan <chandarren@pigweed.infra.roller.google.com> | Sat Mar 30 08:44:38 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 30 08:44:38 2024 +0000 |
| tree | 7a387ff219a38d8ee1dbe0c876c56a7afc95b559 | |
| parent | 3354188924cebb720789cdc22e53f08d219a8917 [diff] |
[roll third_party/pigweed] pw_bluetooth_sapphire: Fuchsia testing support Add support for testing on Fuchsia by performing the following: 1. Introduces the fuchsia-infra-bazel-rules repository as @fuchsia_infra, allowing us to use `fuchsia_test_group` to run all target tests under the scope of a provisioned emulator. 2. Uprrev @com_google_googletest (gtest for Bazel) to contain 3b6d48e8d5c1d9b3f9f10ac030a94008bfaf032bb. This is needed to realize the upstream changes necessary to build gtests that run against a Fuchsia target. Original-Bug: 331692493, 42178254 Original-Fixed: 321267689 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/198270 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 16c27d8785cb548..314a6228d8b6aa8 Roller-URL: https://ci.chromium.org/b/8752054417652198257 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I55e789c41aa546b966cedb85a4f25ab26bbdab0e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/201170 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.
For more information see the Pigweed Getting started guide.
Check back for more complex examples and features coming soon!
Make sure you've set up Pigweed's prerequisites.
If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:
curl https://pigweed.googlesource.com/pigweed/sample_project/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64
Then you can run the script with the following command in cmd.exe:
setup_pigweed_prerequisites.bat
Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.
Once that is done, you can clone this project with the following command:
git clone https://pigweed.googlesource.com/pigweed/sample_project
Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.
To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:
Windows
bootstrap.bat
Linux & Mac
source ./bootstrap.sh
After tooling updates, you might need to run bootstrap again to ensure the latest tools.
After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.
Windows
activate.bat
Linux & Mac
source ./activate.sh
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
When you pull latest repository changes, run bootstrap:
source ./bootstrap.sh
If you're just launching a new shell session, you can activate instead:
source ./activate.sh
and rebuild with:
pw build
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.