commit | 3a88f2f791a28b8826955ee0141d6a1aeebf0385 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sat Aug 09 22:38:46 2025 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Aug 09 22:38:46 2025 -0700 |
tree | eb2d24add31552d7800beb7edac3b54b4ac8846b | |
parent | f1c1fb6fa807b34b459690040650323420559a32 [diff] |
roll: third_party/pigweed roll: python-wheel 310 From git_revision:77ec8928648a0d315499ac3b7df03f29f6ba9a9a To git_revision:0bc94e4dff43a067f9a5cd418e390569251ca527 311 From git_revision:77ec8928648a0d315499ac3b7df03f29f6ba9a9a To git_revision:0bc94e4dff43a067f9a5cd418e390569251ca527 Roll-Count: 2 GitWatcher: ignore Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/311543 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Original-Revision: 18c001d1d0f5127aecd3f760d8e61c1c46d2d01b Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 31658283493e83..18c001d1d0f512 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8706948758018665281 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5ad9d7fc18aba71cf8b62e881631b68892d5ed5e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/311205 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
.