roll: third_party/pigweed a007cbf..38d7504 (9 commits) 38d7504:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314321 pw_protobuf: Callback API for encoding bytes fields c786b58:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314478 pw_chrono: Use Message.FromString() rather than ParseFromString() fbeb306:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314477 pw_thread: Use Message.FromString() rather than ParseFromString() 523fffe:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/313132 pw_containers: Mutable access to InlineVarLenEntryQueue 03fce0f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314476 pw_cpu_exception_risc_v: Use Message.FromString() 1a484a0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304795 pw_trace: Add Zephyr backend for trace time f3e8472:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/304458 pw_thread_zephyr: Move sleep_until to inline header 887dd01:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314475 pw_cpu_exception_cortex_m: Use Message.FromString() 4222575:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/314474 pw_snapshot: Use Message.FromString() rather than ParseFromString() Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: a007cbf0ef6cb9..38d750475c923a Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8705988147208361585 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I3af2c1c6b930e640ae297573e0e7f701c15da0d1 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/314692 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.