| commit | 6e7bb54c170b07b0fd3da629e560664541676b6b | [log] [tgz] |
|---|---|---|
| author | Sarah Bodin <sarahbodin@pigweed.infra.roller.google.com> | Fri Apr 25 09:22:33 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 25 09:22:33 2025 -0700 |
| tree | c52d0b2aee289aec81db3c5fc1cd6611af09566d | |
| parent | 17bf0c58217ce1825328715bdb4fc9dfcff9b485 [diff] |
roll: third_party/pigweed pw_bluetooth_sapphire: Implement IsochronousStream::Write() Implement support for Write() with tests. Original-Bug: 311639690 Test: bazelisk run --config=fuchsia //pw_bluetooth_sapphire/fuchsia/host/fidl:test_pkg Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/262793 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: c65f4c1775310862bc66881e5ce48977bd118db9 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 517b964d0349d1..c65f4c17753108 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8716602130454156049 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Idf87d0d26c8a37a5564c504c99b557c7e4d1dbd3 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/286495 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.