| commit | 9577f3926c660af295f6ee9c4fd0cb764d3c55f1 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jan 10 12:42:46 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 10 12:42:46 2025 -0800 |
| tree | 7d341779c7755855de3db8863f8c9ea13493247c | |
| parent | c948702c4e57a0374a82acab0dadc4d25a72c850 [diff] |
roll: third_party/pigweed 72d815e..6148e5f (8 commits) 6148e5f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259112 pw_bluetooth_sapphire: Add PairingTokens to Peer 3cb02e2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259692 Revert "pw_presubmit: Use CQ cache instance" a9e3ab0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259335 Revert "pw_presubmit: Add remote_download_outputs kwarg" fc439e5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/193051 targets/emcraft_sf2_som: Fix runtime stats 03630c8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/257692 pw_protobuf: Correct nested scratch buffer size order of operations 18ba033:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259415 pw_bluetooth_sapphire: Fix header not found error in mock_server.cc ec95722:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259432 pw_protobuf_compiler: Add GN argument for generate protos 664160e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258353 pw_bluetooth_sapphire: Add helper for checking key validation support Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 72d815eed764e4..6148e5f047c685 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8726098505897401921 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id292d97ffea09d1a62870bb3654f022b78c30a21 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/259752 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.