roll: third_party/pigweed 309122c..c59d362 (7 commits)

c59d362:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/338953 pw_bluetooth_sapphire: Move A2DP offloading opcodes to Emboss
2cdb8d4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441634 pw_metric: Fix ClangTidy include-cleaner warnings
c9a4fa8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440072 pw_toolchain: Suppress -Wunused-template globally
07f9d86:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441693 pw_async2: Fix coroutine_handle ABI mismatch
70189e4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441472 pw_snapshot, pw_system: Plumb snapshot cpu_arch to LlvmSymbolizer
e0f05e9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441357 pw_bluetooth_sapphire: Fix unbounded memory growth on invalid PA reassembly
d4f44dd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441356 pw_bluetooth_sapphire: Limit DataElement recursion

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 309122cf91682b..c59d362bf0d288
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8675439197564789857
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic2e2be34ab649cfb37ae791c7d581fa153f83334
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/441952
1 file changed
tree: dc129ea798718aa564caec989659257c8a9204a9
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .bazelignore
  11. .bazelrc
  12. .bazelversion
  13. .clang-tidy
  14. .gitattributes
  15. .gitignore
  16. .gitmodules
  17. .gn
  18. .pw_console.yaml
  19. activate.bat
  20. banner.txt
  21. bootstrap.bat
  22. bootstrap.sh
  23. BUILD.bazel
  24. BUILD.gn
  25. BUILDCONFIG.gn
  26. LICENSE
  27. MODULE.bazel
  28. navbar.md
  29. OWNERS
  30. pigweed.json
  31. pw
  32. pyproject.toml
  33. README.md
  34. ROLLER_OWNERS
  35. workflows.json
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/examples/+/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/examples

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.