roll: third_party/pigweed f4a43d1..71726ae (9 commits) 71726ae:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/434643 pw_bluetooth_sapphire: Implement repeated attempts backoff in sm c86a84d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440254 pw_chrono_zephyr: Migrate to strip_include_prefix 3f7a576:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440253 pw_thread_zephyr: Migrate to strip_include_prefix 95bfb93:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440252 pw_sync_zephyr: Migrate to strip_include_prefix 209813b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/439895 pw_chrono_zephyr: Isolate backend override headers 8500413:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/439894 pw_thread_zephyr: Isolate backend override headers cf68240:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/439893 pw_sync_zephyr: Isolate backend override headers 556c2dd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/436532 pw_tokenizer: Respect length specifiers when decoding integers in Rust 9ae22d9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/433955 pw_bluetooth_proxy: Handle parameters without prior enable gracefully Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: f4a43d14579711..71726ae1d0bb25 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8675536223741953025 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ic96eea9cac6e3c98eede8af5a708b074a03be211 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/440972
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/examples/+/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/examples
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.