| commit | e5031be46ee17860b8893f42c7fceeb55e93230d | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 03 05:52:59 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 03 05:52:59 2024 +0000 |
| tree | 1a7ac0cab351d79ce293e2869f8be9f0af4cddb2 | |
| parent | eb36301737583feebbcd566794e6c4f1a8f687d0 [diff] |
roll: third_party/pigweed: pw_bluetooth_sapphire: Refactor LowEnergyScanResult to its own class The LowEnergyScanResult class was previously a struct with all public members used to track the elements related to a scan result. A bit awkwardly, the advertising data and scan response data related to the scan result was stored in LowEnergyScanner::PendingScanResult. This change updates LowEnergyScanResult to store the advertising data and scan response data within itself. To present a better API to users, and to prevent accidental modification, LowEnergyScanResult is now a class with getters and setters instead of a struct with all public members. Since LowEnergyScanResult stores the advertising data and scan response data itself, we can also modify the LowEnergyScanner::Delegate::OnPeerFound API to simply take the LowEnergyScanResult alone instead of also taking in the data as a separate argument. We only did that because the data was stored separately. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/987909 GitOrigin-RevId: 9b3b47f13c3c8b41c4a00fe4a2d2a2688b9a807c Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218975 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 5c3289c29896ea2..f219e65ac4075ab Roller-URL: https://ci.chromium.org/b/8743458862133184833 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I72fa1d5fcd7b89b77b5b5c75478b0d207548b838 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/220051 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>
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!
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
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
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
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
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.