| commit | 00d1d18eb81dfd31b4cecc3dcae3cc4f8faadd97 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Feb 27 11:21:48 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 27 11:21:48 2025 -0800 |
| tree | 37222e38b38144edbd9c4c7896e75d9daeadcbcc | |
| parent | c24aed574994b13ebb6e2a9833cd1464a0f4372e [diff] |
roll: third_party/pigweed c75b4f3..9814a13 (7 commits) 9814a13:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271372 pw_allocator: Simplify block unit test trait assetions 48cfde5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271152 pw_malloc: Remove build file variables 8b4d2d5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271473 pw_kernel: Add Cortex-M33 mps2-an505 QEMU platform 89e33bd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/270413 .*: Replace pw_assert dependency e3c7b6b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271472 fuchsia_sdk: Replace fuchsia_sdk load statements with rules_fuchsia d643928:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271592 pw_trace: Fix typo, add missing macro to doc 23b9953:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271353 pw_rpc: Add console RPC completions from modules Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: c75b4f3ea9c830..9814a13fd48140 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8721755653049407729 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5313eae30ad4e6a59b789f1990822e3958e8e40c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/271693 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.