Google Git
Sign in
pigweed / pigweed / examples / af908bcc7a6f08dce5030e5eb68c7d23eea70f2f
commitaf908bcc7a6f08dce5030e5eb68c7d23eea70f2f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 14 14:27:25 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 14 14:27:25 2025 -0700
treecc50064d7c7bdb89752fa39c01f0284d5290e856
parent7ca4155b1e45c2cc11984b011c8034c8dd75e9a7 [diff]
roll: third_party/pigweed 1d18412..0171dbf (7 commits)

0171dbf:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/290891 pw_bluetooth_sapphire: Calculate Peer::identity_known()
e0b9afb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/286636 pw_i2c_linux: Add Android.bp and pw_i2c_linux target
a59058e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/286635 pw_i2c: Add pw_i2c target to Android.bp
95e5829:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/284232 pw_i2c: Rework backward compatibility for message interface
8611aa3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/291357 pw_toolchain: Add new CTAD warning
ba3e462:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/291274 pw_build: Update all Pigweed Android.bp to support cmake snapshots
3df6583:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/291019 pw_ide: Update .gitignore for files generated by pw_ide extension

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 1d184121752dbc..0171dbf2005808
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8714861715567941297
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9f0348c3d6683e90c89d4d77859913aa2cb38b34
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/291492
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: cc50064d7c7bdb89752fa39c01f0284d5290e856
  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.