| commit | 3f69ad56aad23724ef03876bbc7e8a0088f8d164 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Mar 24 16:55:35 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 24 16:55:35 2025 -0700 |
| tree | 12c0856e1e3105473568ddcd15c5fb5fb91ffe74 | |
| parent | 5722da63abe5c5a759a0e1cc927cacf554f6b24e [diff] |
roll: third_party/pigweed 244b3d0..3003d35 (6 commits) 3003d35:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278454 pw_bluetooth_sapphire: Re-enable UBSAN tests in sm c658b93:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278393 pw_bluetooth_sapphire: Fix gatt UBSAN failure 3ccc4c6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278453 pw_bluetooth_sapphire: Remove outdated TODO 011a081:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/274695 pw_bluetooth_proxy: Implement L2CAP configuration request handling 096b4e7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276332 pw_bluetooth_sapphire: Return credits after reading 5fd1e1f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278377 docs: Warn about LED not working on Pico W Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 244b3d0399b3d6..3003d35d53be38 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8719472747013286513 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iaea012a19f25d9513fa776bb98d3b026f44a1e3f Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/278474 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.