| commit | ff48a21080e562ac7f86baff571d51c22fab2687 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue May 13 14:29:25 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 13 14:29:25 2025 -0700 |
| tree | 095b37edfe0e8ee027328e1ae76907a632d781e4 | |
| parent | 05a19d30bca979658b649d3bfe80f765649e3789 [diff] |
roll: third_party/pigweed b092974..7392869 (9 commits) 7392869:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290582 pw_bluetooth_proxy: Remove ProxyHost::SendGattNotify 9852071:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290581 pw_bluetooth_proxy: Subsume WriteToPayloadQueue into WriteLocked c88b795:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290580 pw_bluetooth_proxy: Remove UsesPayloadQueue fa9344b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290579 pw_bluetooth_proxy: Remove l2cap send queue eb2e86f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289518 pw_build: Pass --no-banner on to --watch bd71cff:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289817 pw_bluetooth_proxy: Move gatt channel to using payload queue 0a0649f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290953 pw_containers: Mark test_helpers as testonly d5c8140:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289974 pw_bluetooth_sapphire: Use async::Dispatcher for clock in ISO b8c2438:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289874 pw_bluetooth_sapphire: Add wake leases to IsoStream Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: b092974ef45eba..7392869f1b00ce Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8714952125776451009 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I99c90624b1d1fa73289e9fcf10290b865937a672 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/291032 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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.