roll: third_party/pigweed 66c46ac..1e1f16e (12 commits) 1e1f16e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317113 pw_rpc_transport: Correctly track the number of total packets 902cb0b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316619 pw_bluetooth_sapphire: Create IsoGroup 5d550d2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316618 pw_bluetooth_sapphire: Fake more functionality in FakeIsoStream fcca8df:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316617 pw_bluetooth_sapphire: Add test packet to create CIS 788829b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316616 pw_bluetooth_sapphire: Add test packet for config CIG event dd63e84:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316615 pw_bluetooth_sapphire: Add test packet to create/config CIG 9e9c54d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317172 pw_bluetooth_sapphire: Add static_size() for StaticByteBuffer 5468890:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316614 pw_bluetooth_sapphire: Add OpCodes for creating CIG/CISes 4587c39:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316613 pw_bluetooth_sapphire: Add types for creating CIGs/CISes 0113cf0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316612 pw_bluetooth_sapphire: Fix warnings in FakeIsoStream b9d4927:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314273 pw_bluetooth_sapphire: Add interface for creating CIS for CIGs 2202248:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/316354 pw_containers: De-macro inline_var_len_entry_queue_test Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 66c46ac950f2ac..1e1f16e0eaf184 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8705242243573505921 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iccaa5240ecc71555910bcd486a23e8bd18f41ca4 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/317111 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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.