| commit | 7bd9ee5d545ec01616b0af8d84984143a5f5d212 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Oct 21 13:04:30 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 21 13:04:30 2025 -0700 |
| tree | a9d58a75428a3770e2d774e131b5e6205c6ed9fa | |
| parent | 56506c426ca695b894bffdba1a525d6c82db9ada [diff] |
roll: third_party/pigweed 113773d..6a93fbd (8 commits) 6a93fbd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/332856 pw_containers: New Deque and FixedDeque classes 3784afc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/332513 pw_transfer: Wait for handler registration to complete 781bb0d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/335693 pw_ide: Add nop performance regression test 783059f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/336172 bazel: Roll Pico SDK 8e1d5fd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/336134 pw_ide: Increase VSCode test timeout to 6 minutes 43b338d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/336132 pw_kernel: Use u64 to represent addresses in system_generator 8de330f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/332412 pw_build: Export artifacts d62d9a0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/336032 pw_grpc: Move SendQueue to be owned by Connection Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 113773d896c90a..6a93fbde60f94e Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8700371340027194881 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I3fd25e5ccb98cbe4262682bd240061f2a922d63d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/336234 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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.