Google Git
Sign in
pigweed / pigweed / examples / 08b91e8d725e6617a106a4abc9d8a26f993b313f
commit08b91e8d725e6617a106a4abc9d8a26f993b313f[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Thu Sep 11 00:04:08 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Sep 11 00:04:08 2025 -0700
tree7735474fb75d2d7516bb5b40c272bc1085c22d0c
parent7cdbb3d63f62a947e24f93449fd96d55d0458242 [diff]
roll: third_party/pigweed c34cb4e..540b923 (10 commits)

540b923:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/321175 pw_bluetooth_proxy: Use flushable flag for to-host ACL packets
0462a9b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/319852 pw_bluetooth_proxy: Reduce log level for acl disconnect
a0c0584:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/319236 pw_bluetooth_proxy: Add gtest repeat instructions
cda169b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317141 pw_bluetooth_proxy: Use libc in multibuf allocators for testing
16a14de:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317139 pw_bluetooth_proxy: Multi-threaded write tests
749dc69:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317140 pw_bluetooth_proxy: Move PopFrontPayload after all usages
4a55e5a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317138 pw_bluetooth_proxy: Add some more logging around l2cap write
d765d7c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/317137 pw_bluetooth_proxy: Share kTestL2capQueueCapacity across tests
fccd3fb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/295175 pw_bluetooth_proxy: Avoid running drain if already running
673b243:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/295114 pw_bluetooth_proxy: Mutex new_tx_since_drain_

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: c34cb4ead63acf..540b923c209bd0
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8704044323793265393
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I14689ca0a79a07ee604df301f193f5facaac40d6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/321374
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: 7735474fb75d2d7516bb5b40c272bc1085c22d0c
  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.