| commit | f1e212bb7c24239fa0f4d7270106345aff4d46ee | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed May 21 14:05:51 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 21 14:05:51 2025 -0700 |
| tree | 4ce37dd818d8f71baa1bcbfae1890d0a6447c1a6 | |
| parent | f3dda0b990f781c603f258d477ca14ad1025316d [diff] |
roll: third_party/pigweed 121a101..654e456 (13 commits) 654e456:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289515 zephyr: Migrate to new test framework b09da2b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292458 pw_bluetooth_proxy: Delete unused includes 15349ff:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293395 pw_rpc_transport: Correct simple_framing_test std::equal() checks b102538:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293394 pw_rpc_transport: Use ByteBuffer to access SimpleRpcPacketEncoder header ebc860c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293393 pw_rpc_transport: Correct SimpleRpcPacketEncoder kMaxPacketSize check 72ed9eb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293392 pw_rpc_transport: Add kMaxEncodedPacketSize to SimpleRpcPacketEncoder 6646eb1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292972 pw_rpc_transport: Add BaseRpcEgress d3f422a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293492 pw_bluetooth_sapphire: Initialize logger dee4878:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289514 pw_i2c_zephyr: Add Zephyr backend for i2c bc15bc2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292461 pw_bluetooth_proxy: Move event_fn to ChannelProxy bb2347b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292457 pw_bluetooth_proxy: Introduce ChannelProxy and related classes db5c5ff:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292833 pw_bluetooth_proxy: Refactor client channel tests into their own file fa9e18c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/292456 pw_bluetooth_proxy: Group l2cap variable declarations Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 121a1012a5ea6b..654e456b4749b7 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8714228819820666913 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I1cf3df6af53105e7baa4faf0492d92632380e2ab Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/293442 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.