Google Git
Sign in
pigweed / pigweed / examples / b6b7eb8be153b40b151161368828df962fae564f
commitb6b7eb8be153b40b151161368828df962fae564f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jan 09 12:45:36 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 09 12:45:36 2025 -0800
tree0dcc1e48dc186f7d04b49c4014a12f95d79defe9
parent970624db2bbff9150335ebef455dd50478c33a47 [diff]
roll: third_party/pigweed 4a2fd44..7f196d0 (9 commits)

7f196d0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259173 pw_bluetooth: Normalize two OpCode command names
5c4455c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256432 pw_allocator: Use std::lock_guard in sync_alloc
a7f27b5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259172 pw_bluetooth: Add more OpCode definitions
17c1509:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257114 pw_bluetooth_proxy: Update round robin approach
df36f07:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254433 pw_toolchain: Cleanup transition flag
78a218f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259252 pw_build: Remove old flag requirement
d3a0a19:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259153 pw_bluetooth_sapphire: Use emboss OpCode in RespondWithCommandStatus
049545e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259152 pw_bluetooth: Add more OpCode definitions
7cc8be0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259113 pw_bluetooth_proxy: Change HandleFragmentedPdu name back

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 4a2fd44d2b0ade..7f196d0ba6bde0
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8726188918827260097
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibe56ff9330dbc2c84d259bd61f5b2a60dd5b09bf
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/259393
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: 0dcc1e48dc186f7d04b49c4014a12f95d79defe9
  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.