commit | d72960d04081f74d066d8e1da8f1b35b88051536 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jan 08 15:49:37 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 08 15:49:37 2025 -0800 |
tree | a0878fa3238bcbfb1bd3c5bce8202c868856464f | |
parent | 6397a869d36d2775fe9a2e06850b777d9cffe9cc [diff] |
roll: third_party/pigweed a16e8fa..aef6fca (12 commits) aef6fca:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/251712 pw_tokenizer: CSV parser 483a24a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/229672 pw_crypto: Remove micro_ecc support b03ff49:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258772 pw_bluetooth_proxy: Allow Write(MultiBuf) for gatt notify 56d9d44:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258712 pw_bluetooth_proxy: Allow Write(MultiBuf) for rfcomm and basic b129282:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258533 pw_bluetooth_proxy: Move Write(MultiBuf) to L2capChannel 88e93b8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258422 pw_bluetooth_proxy: Rename L2capChannel incoming functions to use Handle 9925b31:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258456 pw_bluetooth_proxy: Move functions to protected 0f95b66:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258454 pw_bluetooth_proxy: Remove deprecated L2apCoc::Write(span) 413a815:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/252472 pw_toolchain_bazel: Remove contents 3e0b832:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258833 docs: Remove admonition about Bazel version pin 736d6a3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/239049 pw_fuzzer: Make FuzzTest usable be external CMake projects 0a9be2a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256116 pw_bluetooth_proxy: Remove old cid fields Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: a16e8fa9d3de1d..aef6fca14a9c0c Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8726268026447559185 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8bece99595dec0ac60cebd4399cf2a396f9a2182 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/259075 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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
.