Google Git
Sign in
pigweed / pigweed / examples / aa009d3b692e9f651d571ff4b316d1e4290e9571
commitaa009d3b692e9f651d571ff4b316d1e4290e9571[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 17 10:17:31 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 17 10:17:31 2025 -0700
tree6a7cd5538d35270eec1046712d3d10d9fb139a9f
parent7b7b527a798ce5821a62cb464c46ac0853dfd1c9 [diff]
roll: third_party/pigweed fb080e7..b50149b (4 commits)

b50149b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298932 pw_containers: Provide DynamicVector::erase
3f68bc4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298292 pw_containers: Implement erase for InlineDeque and DynamicDeque
efc7493:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298953 pw_result: Remove unnecessary & and && overloads for Result::status()
0df2afe:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298972 pw_env_setup: Update CIPD

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: fb080e7c3d4e48..b50149b80cbc0f
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8711797117036485441
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I750038c7714b93c4277f0b724bce8ced01557469
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/299232
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: 6a7cd5538d35270eec1046712d3d10d9fb139a9f
  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.