Google Git
Sign in
pigweed / pigweed / examples / 371ee4ed7b9419dfd4bc6c7db654cfb4a105cb78
commit371ee4ed7b9419dfd4bc6c7db654cfb4a105cb78[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Aug 30 01:17:30 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 30 01:17:30 2024 +0000
treeb9749a67f8b41225bbea857391d73c82b5361ac0
parent4ba8a61c76aef04e65ff57c395b7d70f51d1610a [diff]
roll: third_party/pigweed: pw_bluetooth_sapphire: Reland "Integrate LegacyPairingState with ..."

Reland "Integrate LegacyPairingState with ..." PairingStateManager"

This is a reland of commit 31a9d97a99e1571ad674961a0647b3de85d9265e

Relanding this with no changes. Originally reverted because there was no
configuration to disable/enable legacy pairing (added in fxr/1102453).

Original change's description:
> [bt][gap] Integrate LegacyPairingState with PairingStateManager
>
> This CL wires up the legacy pairing process code to the rest of the
> system via the PairingStateManager.
>
> Depending on the pairing events we encounter before/after the ACL
> connection is complete, or depending on the result of interrogation with
> the peer, we will tell the PSM whether to use SSP or legacy pairing.
>
> Bug: b/42173830
> Test: fx test //src/connectivity/bluetooth
> Manual Test:
> - Paired and streamed audio to/from Nelson DUT with iOS and veho devices
>   supporting SSP to ensure SSP still functions
> - Paired and streamed audio to/from Nelson DUT with iOS and veho
>   devices. Cherry-picked fxr/1078858 to simulate legacy pairing
>
> Change-Id: Ibf745d6452b5f8fc53dbd16101f2cc3d6a20c114
> Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1062293
> Reviewed-by: Ben Lawson <benlawson@google.com>
> Reviewed-by: Marie Janssen <jamuraa@google.com>
> Commit-Queue: Lulu Wang <luluwang@google.com>

Original-Bug: b/42173830
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1102393
GitOrigin-RevId: 52ee3d21a3b09f3139ec8b30681ca92e760350d4
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/232771

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 7dabba55efacd17..fe1758863affc08
Roller-URL: https://ci.chromium.org/b/8738221150253829489
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I695219fdc0ed605459d3b829bf1d5e92a8b3b77b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/232565
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: b9749a67f8b41225bbea857391d73c82b5361ac0
  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.