Google Git
Sign in
pigweed / pigweed / examples / 61c6dda6043134ad13a08166cc10f826ec0af6ec
commit61c6dda6043134ad13a08166cc10f826ec0af6ec[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed.infra.roller.pigweed-service-accounts.iam.gserviceaccount.com>Sun Mar 02 08:01:30 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Mar 02 08:01:30 2025 -0800
treef5807eed620e3613b95ed0c913e2161a157cd6dd
parent4fe9fdfe9040713f6ca7b0c203ed9fab9e681e9c [diff]
roll: third_party/pigweed roll: luci

bb
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

luci-auth
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

gerrit
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

gitiles
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

cas
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

led
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

swarming
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0e309dced1ad4ba7a80d8e7c313b062c6cc55eeb

logdog
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

prpc
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

luci-cv
From git_revision:0cddbdc27507a17134e1e038f938b62d0f509756
To git_revision:0b7452af1e6d1ef1426bd9000914754f006370cd

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

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 8b96594dffa2c0..7dd375c196e150
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8721495721493154993
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic35f9ff2eea57467f148df0c6e1122224282d5b0
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/272342
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>
1 file changed
tree: f5807eed620e3613b95ed0c913e2161a157cd6dd
  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. .gitattributes
  16. .gitignore
  17. .gitmodules
  18. .gn
  19. .pw_console.yaml
  20. activate.bat
  21. banner.txt
  22. bootstrap.bat
  23. bootstrap.sh
  24. BUILD.bazel
  25. BUILD.gn
  26. BUILDCONFIG.gn
  27. LICENSE
  28. MODULE.bazel
  29. navbar.md
  30. OWNERS
  31. pigweed.json
  32. pyproject.toml
  33. 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.