roll: third_party/pigweed 802a7cb..0dfa004 (9 commits) 0dfa004:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/491151 pw_buf: Add base_size() accessor to Buf 0b47688:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/497216 pw_rpc2: Avoid reentering a connection while destroying it 326b7aa:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/499213 pw_atomic: Redefine asm to __asm__ to fix specific zephyr compilation. 45372fc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/497215 pw_rpc2: Don't reassign the connection on handshake 1c624c6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/497214 pw_rpc2: Share the connection task poll loop 448c2cb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/500773 pw_cli: Suppress banner for automated tools and AI agents 028dc1b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/499273 pw_rpc2: Clean up C++ build targets and dependencies 47e5c14:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/496834 pw_bluetooth_proxy: Validate L2CAP config options 66c7f0b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/499393 pw_assert_tokenized: Check for empty static macro at expansion time Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 802a7cbb62b4cd..0dfa00448df606 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8668110234971887313 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I07765904d3c765c81c66eeab4f0d3a30e14d1e4b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/500973
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/examples/+/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/examples
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.