| commit | 116599325dfb4b148c6cb0c80f567c7cc8a6cf3f | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Sep 29 17:09:52 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 29 17:09:52 2025 -0700 |
| tree | 932e2189ac3cc20afcef6820559b088b8ceecfd3 | |
| parent | 240fbd1dce7c928a1b67f8eb0a8b5ff5f58ce6a8 [diff] |
roll: third_party/pigweed dfcbdf3..b4bf100 (8 commits) b4bf100:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327153 pw_transfer: Fix -Wshadow findings 8ffc27e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327073 pw_thread_zephyr: Drop `Native` prefix from pw::thread::zephyr types 37095cc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327072 pw_thread_zephyr: Create pw::thread::zephyr namespace a524ee0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/326942 flasher: Add the successfully flashed message for debug probe 1c226bd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327172 docs: Update factory docs to be consistent with bazel flash target bdfa95f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327015 pw_env_setup: Rev python deps in preparation for AirLock 39ca78d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327152 pw_bluetooth_{proxy, sapphire}: Fix -Wshadow findings e1e9588:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/327112 docs: Update GitHub mirror URL Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: dfcbdf39af0139..b4bf10078cf875 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8702349099873198961 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5ce43feffa36f009ef0c2abcd0e2a03099207340 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/327134 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.