| commit | ca46b776aeab508a2ae58df6ab99b9da1d9cc2cc | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 30 17:10:33 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 30 17:10:33 2025 -0700 |
| tree | f82b036bae0890ba74ad2a7c86a776c615c92ec6 | |
| parent | 694a75fd3556aeb262d2a0a0916c809e237d9200 [diff] |
roll: third_party/pigweed 1a79f1e..d3cba10 (6 commits) d3cba10:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309732 pw_cpu_exception_cortex_m: Access cortex_m regs via function 5efc915:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309760 pigweed.json: Add docs build to bazel_presubmit 5e40b7c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309442 doxygen: Document namespaces cdf12ab:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309815 rust: Changes to support rust toolchain roll 12964cd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309932 pw_kernel: Remove multiple calls to Target::console_init() e59efb0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309814 pw_bloat: Update Rosetta 2 check Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 1a79f1e8872eaa..d3cba105a6b196 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8707875472710806513 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ibbfce39ccf9e43cd4181eb65e6d493d8cbca66e8 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/309798 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.