Google Git
Sign in
pigweed / pigweed / examples / b7673bd6d2d563a7ac846ca8f88fa0e0d8161f50
commitb7673bd6d2d563a7ac846ca8f88fa0e0d8161f50[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Mar 07 19:45:09 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Mar 07 19:45:09 2025 -0800
tree415329222563016370ee5e6e38ac95d1d8701e59
parent797562156f591d487e996f75fb46124343daf38c [diff]
roll: third_party/pigweed 19b092e..3fa32a8 (9 commits)

3fa32a8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255134 pw_i2c_mcuxpresso: Convert to new i2c initiator message interface
bce90ae:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/260974 pw_i2c_mcuxpresso: Use non-blocking i3c operations
7d88fb9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259973 pw_i2c: Split Message::GetData() into const and non-const version
2dc5872:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259972 pw_i2c: Add feature support to Initiator class
8c78d5f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255133 pw_i2c: Change initiator to take a list of messages for one transaction
287133e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/260059 pw_i2c: Improve TenBit support in Address class
28fdb0a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271743 pw_bluetooth_sapphire: Clean up adapter logs
870f8f8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/260225 pw_bluetooth_sapphire: Add BidirectionalMap
39b8e48:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265638 pw_bluetooth_sapphire: Add operator== to DiscoveryFilter

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 19b092e60ebbaf..3fa32a86aa204d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8720998440332375761
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I24a70935fca113d8af94c927321947bdfba35696
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/274192
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: 415329222563016370ee5e6e38ac95d1d8701e59
  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.