| commit | d46fe2756eb4d9884db3a9b444c455c2019030b4 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jul 29 11:13:39 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 29 11:13:39 2025 -0700 |
| tree | 7d2f1855d1f33962bd70abf42ed276471e01758a | |
| parent | 41bc217ec92cccbf3088ebc9fc2f660344da12b5 [diff] |
roll: third_party/pigweed 89632ab..72d8343 (6 commits) 72d8343:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307906 pw_bluetooth_sapphire: Add periodic advertising test packet helpers 8416642:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307976 pigweed.json: Add pylint to Bazel lintformat e8ad179:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307958 python: Exempt some packages from pylint a63c930:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309472 Revert "docs: Enable Doxylink" 2889f70:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/308273 pw_multibuf: Remove ResizeTopLayer from v2 86a146f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307875 pw_sync: Move test utilities Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 89632abe096e07..72d83431ea7205 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8707988494820000993 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I95bc11471a9a5ee27b440a5992b0d42bacf6cbb2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/309533 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.