| commit | 29a0bc0eecb961007d8e1342edbcba206b51bf5c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Aug 21 16:05:10 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 21 16:05:10 2025 -0700 |
| tree | 7efb3f3067bfc9130de7214df4d55c75a9e44459 | |
| parent | d9d5a9a8fdc850d90e0f89ea8d071ac005abba2b [diff] |
roll: third_party/pigweed 7dc5bad..7997384 (9 commits) 7997384:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314732 workflows: Change some tools to GENERAL type 1272c8a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314997 pw_kernel: Remove forcing opt mode a75fe59:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314993 pw_containers: C++ polyfill of constexpr pw::fill and pw::fill_n 8282c33:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/313652 pw_thread: Avoid creating thread stacks on other stacks 1f9ad05:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/312695 pw_kernel: Add object declaration to system manifest 266056a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/313452 pw_trace_tokenized: Add facade for locking 2345710:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314741 pw_env_setup: Respect CIPD_CACHE_DIR in Bazel c5cb259:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314635 pw_kernel: Add helpers for declaring static ForeignBox and ForeingRc 9ab3e0c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314634 pw_kernel: Add upcasting support for ForeignRc Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 7dc5bad7ae1fdc..7997384514813d Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8705886432606574881 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0f672d21ff2aee1c9ba897349729a08888b6b11c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/315132 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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.