Google Git
Sign in
pigweed / pigweed / examples / refs/heads/main
commit6b626990f6aa6c25cae7c5d0834e69d591d0484a[log] [tgz]
authorLloyd Pique <lpique@pigweed.infra.roller.google.com>Thu Jan 29 21:55:48 2026 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 29 21:55:48 2026 -0800
treee1889fa44c10476f46b69127a34dd63c70563f96
parent9a23cbec58f978611f2fecb27967eaef6b667787 [diff]
roll: third_party/pigweed Revert "roll: rules_python to 1.8.3"

This reverts commit b66ca60f1a31c726dca08d01dde2a599ffcd7e58.

Reason for revert: pigweed-sidecargoogle-roller failed b/479944823

Original change's description:
> roll: rules_python to 1.8.3
>
> Original-Bug: 393647585
> Change-Id: Ib7a59bd5db4a1d394368e6d70d249159188337a1
> Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/366898
> Copybara-Verified: Copybara Prod <copybara-worker-blackhole@google.com>
> Tests-Not-Needed: Lloyd Pique <lpique@google.com>
> Reviewed-by: Alexei Frolov <frolv@google.com>
> Pigweed-Auto-Submit: Lloyd Pique <lpique@google.com>
> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
> Commit-Queue: Lloyd Pique <lpique@google.com>
> Docs-Not-Needed: Lloyd Pique <lpique@google.com>

TBR=frolv@google.com,copybara-worker-blackhole@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,android-build-ayeaye@system.gserviceaccount.com,pigweed-try-builder@pigweed-service-accounts.iam.gserviceaccount.com,lpique@google.com

Original-Bug: 393647585
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/369653
Original-Revision: 9f4e4e926253258a18f8e988cc1a72ade7cd17d2

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 30915267846116..9f4e4e92625325
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8691274475047840785
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I42cc0b5e75817ff0085dfd32c510a71b9ee1f9c9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/369505
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: e1889fa44c10476f46b69127a34dd63c70563f96
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .bazelignore
  13. .bazelrc
  14. .bazelversion
  15. .clang-tidy
  16. .gitattributes
  17. .gitignore
  18. .gitmodules
  19. .gn
  20. .pw_console.yaml
  21. activate.bat
  22. banner.txt
  23. bootstrap.bat
  24. bootstrap.sh
  25. BUILD.bazel
  26. BUILD.gn
  27. BUILDCONFIG.gn
  28. LICENSE
  29. MODULE.bazel
  30. navbar.md
  31. OWNERS
  32. pigweed.json
  33. pw
  34. pyproject.toml
  35. README.md
  36. workflows.json
README.md

Pigweed Sample Project

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!

Getting started

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

Environment setup

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

Building

All of these commands must be run from inside an activated developer environment. See Environment setup

One-shot build

To build the project, documentation, and tests, run the following command in an activated environment:

pw build

Automatically build on file save

Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:

pw watch

Typical workflow

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

More info and Examples

Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.