commit | d431c1ce402f49f38f8aba4d6c38bb1e227dd53a | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jul 11 15:05:10 2025 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 11 15:05:10 2025 -0700 |
tree | 74c24a36c9a8d3dab9160b69e9837a514577779c | |
parent | 394fe06925a378d73a736a4e6ea2a9e6ee98fdfd [diff] |
roll: third_party/pigweed fe369a2..f770f67 (9 commits) f770f67:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/301892 pw_bluetooth_sapphire: Update driver to dynamic routing fabfb75:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304612 pw_async2: Mark waker macros as nodiscard afe5e94:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304572 pw_toolchain: Fix rustc_srcs_path 00a7ab2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/303956 pw_containers: Size reports for pw::DynamicDeque and std::deque cd17fc4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304313 pw_rpc: Expose server_reader_writer only once 349c4ce:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/303952 gemini: Configure Gemini to respect gitignore 53c06ca:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304312 pw_rpc: Split up internal_test_utils 044a590:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304460 pw_build: Add filter for python transitive test deps e8c49ac:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/293993 pw_bluetooth_proxy: Additional comments around locking Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: fe369a2c960164..f770f6738fe2e1 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8709604611205634929 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I71b5e565d9eba1b73801379076131bc8e5addd99 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/304633 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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
.