roll: third_party/pigweed pw_bluetooth_sapphire: Update ISO initialization Update the isochronous channel initalization code to: * Not try to use Controller class flags to determine controller support for ISO channels. Instead, use the spec-defined controller supported feature bits. * Only set the host flag for ISO support after we have finished initializing the ISO data channels. Original-Bug: 435758610 Test: Manual test of OOBE on sorrel Test: Manual test of OOBE + A2DP src/sink on sherlock Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/310393 Original-Revision: 62e93c5da572a17e6759bac7286f88822bf8dc9e Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 494717f520908d..62e93c5da572a1 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8707344322163086689 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: If24e352160f0c3874c79147525604c582a939d0f Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/310732 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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.