commit | c3bc46907512b472087275f9dbfc8b48ac37262e | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Dec 12 20:06:04 2024 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 12 20:06:04 2024 -0800 |
tree | 4dc62772aab4e5c683c6cce6f481bce794766fe5 | |
parent | 84aae53a9c2a54fe698cf33d4ac959549f68a201 [diff] |
roll: third_party/pigweed 5d83553..96f941b (10 commits) 96f941b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253594 pw_bluetooth_proxy: Move AcquireAdditionalRxCredits to L2capCoc 9cda022:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254212 pw_bluetooth_proxy: Remove state from RfcommChannel aa9a4e8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253556 pw_bluetooth_proxy: Remove deprecated event_fn from L2capCoc 5fc8302:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253520 pw_bluetooth_proxy: Close channels on disconnections in both directions 2592257:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253856 pw_bluetooth_sapphire: Save advertising data buffer after parsing 3e46575:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254112 pw_bluetooth: Add AVDTP_GET_ALL_CAPABILITIES 046c562:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253519 pw_bluetooth_proxy: Close channels on ACL & L2CAP disconnections f58927a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253518 pw_bluetooth_proxy: Close AclConnection instead of erase df92f9f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254020 fuchsia: Introduce @rules_fuchsia 737e613:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253517 pw_bluetooth_proxy: Add running/stopped state to L2capChannel Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 5d83553897b31a..96f941bde9f644 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8728697845766209793 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ibe7f5aa9ede70998dbf467e5190de8564cd0950e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/254333 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>
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
.