Google Git
Sign in
pigweed / pigweed / examples / 96850e30ccf404da801c0afff077756c0950462e
commit96850e30ccf404da801c0afff077756c0950462e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sun Oct 12 08:04:17 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Oct 12 08:04:17 2025 -0700
tree0e8c2f999a78d8c9bcc15939aeefbceee350174c
parent37165d539c6a3703d0f8685e97e4d604ffbf99a1 [diff]
roll: third_party/pigweed roll: luci

bb
From git_revision:03d4e5d329953441580608607f316f62e4de2d7b
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

luci-auth
From git_revision:0583d281c05ff8918dffe3820ed5313213e8030d
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

gerrit
From git_revision:0583d281c05ff8918dffe3820ed5313213e8030d
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

gitiles
From git_revision:0583d281c05ff8918dffe3820ed5313213e8030d
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

cas
From git_revision:0583d281c05ff8918dffe3820ed5313213e8030d
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

led
From git_revision:03d4e5d329953441580608607f316f62e4de2d7b
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

swarming
From git_revision:03d4e5d329953441580608607f316f62e4de2d7b
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

logdog
From git_revision:0aa3972ae5ac53b967da2cd4107c05c5eb4e9241
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

prpc
From git_revision:0583d281c05ff8918dffe3820ed5313213e8030d
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

luci-cv
From git_revision:03d4e5d329953441580608607f316f62e4de2d7b
To git_revision:169b8b52c3bec2357420a207482f4c9788fdd5f6

Roll-Count: 10
GitWatcher: ignore
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/331692
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Original-Revision: b06cdf7b6596645827059ba7e9cb563b8d744942

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 3e53ccf5027db2..b06cdf7b659664
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8701205602249196625
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I463e5bd1efcc7e7a94f3790559e53178b7e20022
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/331752
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 0e8c2f999a78d8c9bcc15939aeefbceee350174c
  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/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

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.