Google Git
Sign in
pigweed / pigweed / examples / fe5f5d1906eed6a39c7cfa4e9e61fd146f1c788e
commitfe5f5d1906eed6a39c7cfa4e9e61fd146f1c788e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed.infra.roller.pigweed-service-accounts.iam.gserviceaccount.com>Sun May 25 07:54:55 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun May 25 07:54:55 2025 -0700
tree946d6c10f961375fd75edc62efc44d6ea289e848
parenta68df66bab279570488ff143d28b65cd307a24f8 [diff]
roll: third_party/pigweed roll: luci

bb
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

luci-auth
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

gerrit
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

gitiles
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

cas
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

led
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

swarming
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:c5d1f48d6baf50f56cb6c5381d861cecd195003f

logdog
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

prpc
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

luci-cv
From git_revision:0187f776e86b46692b599e71b15602cb7e2abde2
To git_revision:021720ebb04c4f86df8910e6273e53d840e5259e

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

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: bfdbef991e679d..d34b1d1996f905
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8713889776416347201
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib6ea3acb58c2ec7ecabb04ff250ebd3c39ea9f6a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/294212
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>
1 file changed
tree: 946d6c10f961375fd75edc62efc44d6ea289e848
  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. pyproject.toml
  34. README.md
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.