| commit | 05173a31a4db146d34631ef6b40e36db6e6cb6c0 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Mar 18 20:11:38 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 18 20:11:38 2025 -0700 |
| tree | 6d004844c0f7e52fb593cefe1abd866929242b48 | |
| parent | 7af104e3c64b9bc4ed8ecad9d2181051f01d69f0 [diff] |
roll: third_party/pigweed 43f76d0..1bfa6aa (6 commits) 1bfa6aa:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276993 pw_kernel: Combine cortex-m and riscv entry points 775445d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276992 pw_kernel: Refactor targets for consistency 29e6e1e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276494 pw_kernel: Don't tick scheduler before there are tasks to run 64d117c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276493 pw_kernel: Add preempt disabling/rescheduling on WakeQueue::wake_one 7c91661:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276492 pw_kernel: Add current_thread accessors 0f7fc56:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/274972 pw_tokenizer: Correctly detect target os for Rust linker section Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 43f76d07aff5eb..1bfa6aa33ce225 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8720003923059158449 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I31f6ee0f07ad7104955dfbe7cfc72f6cd1c8104d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/277092 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.