commit | df33b3776f552d9209f545dc1e43ae2502ad9cc5 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jan 02 16:04:39 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 02 16:04:39 2025 -0800 |
tree | 95b09fcf8bb968354848cf9c14b9e67aec52d100 | |
parent | b93619770f0b9596dde7841ff9587f8f01a19c72 [diff] |
roll: third_party/pigweed 6582c5e..5237640 (10 commits) 5237640:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256092 pw_bluetooth_proxy: Provide IsWriteAvailable function ae9750e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256841 pw_bluetooth_proxy: Don't log dtor of moved-from channel objects 7cac792:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256840 pw_bluetooth_proxy: Remove extra space from some logs 58e24d6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256839 pw_bluetooth_proxy: Log if disconnect with unknown connection 953f10a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257232 pw_multibuf: Fix Android.bp 645d820:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256837 pw_bluetooth_proxy: Rename FindAclConnection to FindOpenAclConnection d4d56ca:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257074 pw_thread_freertos: Assert PW_THREAD_FREERTOS_CONFIG_* are valid 1140dc2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256836 pw_bluetooth_proxy: Add logging for events 2f2d633:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257073 pw_bluetooth_proxy: Add logging for setup and teardown babdb2a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257112 pw_protobuf: Initialize variables in docs example Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 6582c5e54ab2e4..5237640e809cce Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8726810511263299681 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I55a9568988fd2a8f05cdbd104b423f2afe8eb5c9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/257392 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
.