Google Git
Sign in
pigweed / pigweed / examples / bfb8a36e6a309223aad2dc3f700bc4e4d50eace3
commitbfb8a36e6a309223aad2dc3f700bc4e4d50eace3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 03 13:29:54 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 03 13:29:54 2025 -0700
treee2dadb004edf44fb4ac8faab084dcdaca0d7007b
parent6382b6b9bcb867f2b8b3273105e19f8d8e90b27d [diff]
roll: third_party/pigweed de2fc41..f69b7e7 (8 commits)

f69b7e7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/279992 pw_bluetooth_sapphire: Populate advertising fields in peer
cef99cf:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278712 bazel: Update to latest rules_cc
96f1e37:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277752 pw_env_setup: Add some Rosetta logging
e63f000:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280976 pw_kernel: Remove nomem and nostack on interrupt guards
b78d7e2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280975 pw_kernel: Support usize registers
a1f21a8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278012 pw_bluetooth_sapphire: Acquire wake leases in AclDataChannel
7beeec2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280662 pw_ring_buffer: Implement PopBack
c02f54a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/274334 pw_toolchain: Remove WORKSPACE toolchain helper

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: de2fc4187ae346..f69b7e70518055
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8718579923372011729
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ief367d302516892b11df8588533d69e513d6e8da
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/281212
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: e2dadb004edf44fb4ac8faab084dcdaca0d7007b
  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.