| commit | 652e3e56958568d4a9ec5cb603a396afd66483d9 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jun 25 12:53:40 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 25 12:53:40 2025 -0700 |
| tree | e273f38cc6e66e69f14c6ac7667453c36fb21bd2 | |
| parent | 21a2b0d06fcac50370b2703be7589d6652b79bcc [diff] |
roll: third_party/pigweed 9387c75..c45c482 (6 commits) c45c482:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300634 roll: gn 7bec4f6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300375 pw_bluetooth_proxy: Print channel and PDU info in dropped recombine case 6397fa7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298952 pw_toolchain: Add lib/clang/*/share to sandbox 2031c19:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300532 pw_digital_io_linux: Fix bazel layering check f3d952e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300493 pw_elf: Remove conversion_warnings exclusion c09a63c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300492 pw_elf: Fix bazel layering check Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 9387c753737f7d..c45c482f8785b7 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8711062534885259073 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7651c8e258978717b689d254a1f2a8c68f694538 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/300752 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.