| commit | dae85717d98be45db9746c24a4deac5db3f95b96 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Jan 06 12:58:38 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 06 12:58:38 2025 -0800 |
| tree | 24cc903e0cfb20df2a34cd4def53c62f2f327694 | |
| parent | 1b217c7b43f5292155263f780b0d71d2b8c9a117 [diff] |
roll: third_party/pigweed 7940ef2..c3fd517 (6 commits) c3fd517:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258173 pw_bluetooth_proxy: Use switch statement with H4PacketType 8706efb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258392 pw_protobuf: Allow unset callback fields in message structs bfe2c77:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256693 docs: Move bug directive dbf07bb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/258393 pw_toolchain: Add manual tag to supports_pic_old 924b629:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256835 fuchsia_sdk: Use toolchain defined in rules_fuchsia e5e913d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256373 [owners] Remove luluwang@google.com from pw_bluetooth_proxy/OWNERS Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 7940ef25e097da..c3fd51718227f1 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8726460150305159441 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I584fcd15fbf1e4f3f09a9d21ee0440c15a07b068 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/258433 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.