roll: third_party/pigweed e38aff6..1b6dc6a (5 commits)

1b6dc6a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/284313 third_party/chromium_verifier: Use pw_external_chromium_verifier in gn
60b13c1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/285732 pw_tokenizer: Add a few tests; fix typo
d1a9c37:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/285672 pw_bluetooth_sapphire: SCO Offload Index config
ef9eb37:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/285372 pw_rpc_transport: Fix docs.rst example of node B setup
ba96152:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/283972 pw_bluetooth_proxy: Handle l2cap disconnection response direction

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: e38aff6439df47..1b6dc6ad02adf7
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8716850772625723233
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If83ae04c6d9cc60e85bfbe53d5a68e65cc595e82
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/285716
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 84216b1f153b877ad7dfa7984f4a8371e57df03f
  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. pyproject.toml
  32. 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.