| commit | 5b0e8b04c149f00a4352c9f1f3d09ca946c43f0f | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Nov 19 23:16:38 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 19 23:16:38 2024 +0000 |
| tree | a8c0f5c156b607ba5a4e263aa0b822d809f05b7b | |
| parent | 2dac47509a49185871f2590c8088b44a7b86980a [diff] |
roll: third_party/pigweed 76f7aa2..c409392 (3 commits) c409392:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/235493 pw_bluetooth_sapphire: Fix unused parameter warnings 758d608:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/249972 pw_protobuf: Respect max_count when computing kMaxEncodedSizeBytes c389296:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/248152 bazel: Minor WORKSPACE cleanup Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 76f7aa25d19c61..c40939242de4c9 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8730799906843297249 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I40500b83e7f4a51be42fed78bd64ac843370042e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/250195 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.