commit | 837a957f6f33bf41baf9a2fc0365549163e3b5fc | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jan 09 15:44:03 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 09 15:44:03 2025 -0800 |
tree | 942efb47d9756af7a278518a6fc645bc51314c00 | |
parent | b6b7eb8be153b40b151161368828df962fae564f [diff] |
roll: third_party/pigweed 7f196d0..5976c3a (11 commits) 5976c3a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258775 pw_watch: Generic watcher and bazel integration f94267a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259413 docs: Fix figcaption color 09e1696:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259453 pw_bluetooth_proxy: Fix parameter name mismatch clang-tidy error 7cb88b2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259452 pw_bluetooth: Add AVDTP_SUSPEND_CMD 46ce327:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259354 pw_bluetooth: Add AVDTP_START_CMD 7a788dc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259052 pw_bluetooth_proxy: Print hex value of the channel ids b687a64:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258973 pw_bluetooth: Add avdtp set stream command 818f8c1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259032 pw_bluetooth: Emboss util fn for copying from a container 8adc4c3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259412 pw_toolchain: Update m33 float-abi 6a6b22b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259174 pw_bluetooth_sapphire: Use emboss OpCode in RespondWithCommandComplete 203c6c8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259055 pw_unit_test: Expectation buffer cleanup Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 7f196d0ba6bde0..5976c3a78de4d7 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8726177619713220913 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iad71d7fd7673bb9a64923dfe360c16238866ecd0 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/259234 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
.