roll: third_party/pigweed 414050b..7e81e78 (15 commits) 7e81e78:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/502013 pw_async2: Add ValueFuture::MoveFrom for derived futures 0bd3449:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501418 pw_protobuf: Fix implicit conversion warnings 7621f57:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/499796 pw_system: Guard MTU in RpcChannelOutputQueue dd263b9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501433 pw_metric: Fix implicit conversion warnings 6c4e8fe:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501417 pw_random: Fix implicit conversion warnings f72f377:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501374 pw_protobuf_compiler: Enable implicit conversion warnings 07d12a9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501415 pw_unit_test: Fix implicit conversion warnings 9ccf743:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501414 pw_bloat: Fix implicit conversion warnings 849fea0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/500314 pw_ghish: Default Buganizer comments to MARKDOWN 1b63ce7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501318 pw_spi_linux: Fix implicit conversion warnings 647720d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501376 pw_thread: Fix implicit conversion warnings ff5ab20:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501373 pw_analog: Fix implicit conversion warnings a81a480:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501375 pw_software_update: Fix implicit conversion warnings 3b96e84:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/498756 pw_tokenizer: Fix implicit conversion warnings 9a69ba0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/498755 pw_stream_uart_linux: Fix implicit conversion warnings Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 414050ba2a04f9..7e81e78799ffe1 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8668023977138430225 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I921d017d09eb9adb9485001323d29bf3b2608c25 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/501474
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.