Google Git
Sign in
pigweed / pigweed / examples / 92c175fec8cdefbfff39b240d1b03a0989f68fdb
commit92c175fec8cdefbfff39b240d1b03a0989f68fdb[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 29 14:13:25 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 29 14:13:25 2025 -0700
treef787be54bd7c344715ff31a12799d8468cdf5d74
parentd46fe2756eb4d9884db3a9b444c455c2019030b4 [diff]
roll: third_party/pigweed 72d8343..b91cac9 (6 commits)

b91cac9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307903 pw_presubmit: Enable JS/TS formatting from Bazel
f60cb2b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/301392 pw_allocator: Add method to find the largest free block
8c7de10:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307910 pw_bluetooth_sapphire: Create GEMINI.md for host stack
a3d8ef6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309476 pw_build: Fix type in PythonRunfilesLabelAdapter
c72af82:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309432 pw_presubmit: Add toggle flags for all formatters
dac849c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309433 pw_bytes: Clarify restrictions of ObjectAs[Writable]Bytes

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 72d83431ea7205..b91cac90a9a8ae
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8707977196936255873
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I32a102c549b4431b8df6818e21fa241de0a89fc9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/309535
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: f787be54bd7c344715ff31a12799d8468cdf5d74
  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.