| commit | 5764d8febd44a5c7b42a9a8e03f4c27b42f08982 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Aug 11 13:35:24 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 11 13:35:24 2025 -0700 |
| tree | 0a3f84afd3b9e5aa0545c46c387357bc4cbf01b9 | |
| parent | fb112bcec50ef0fb077863bfc4252d1e15078dbd [diff] |
roll: third_party/pigweed 3c25e01..d601bc1 (11 commits) d601bc1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/311540 pw_bluetooth_proxy: Check for null channel rx allocator 415ebf0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/311412 pw_clock_tree: Remove ClockTree class e51744f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/312372 pw_clock_tree_mcuxpresso: Stop using ClockTree in docs and examples 54de344:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/312313 pw_build: Use Label() instead of @@ in mypy aspect dcbb114:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/312312 pw_ide: Remove zxh404.vscode-proto3 as dependency f97f38f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/312292 pw_protobuf_compiler: Remove black dependency 4679013:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/311732 [owners] Remove aharp@google.com from pw_stream_uart_linux/OWNERS 293df77:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309392 pw_uart_mcuxpresso: Drop ClockTree completely 2c94e84:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309393 pw_stream_uart_mcuxpresso: Drop ClockTree completely b3de4b9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309394 pw_i2c_mcuxpresso: Drop ClockTree completely 2f23c98:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/311535 clang-tidy: Add modernize-pass-by-value Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 3c25e0150be62d..d601bc1ec186b0 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8706801835719827041 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ib4c2a6d86ab10ee97edc912c8b2a5a270d31cff4 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/312412 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.