roll: third_party/pigweed 5d3945e..efa36cc (12 commits) efa36cc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/505805 pw_rpc2: Introduce internal::ServiceInfo<ServiceImpl> 95ede28:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/505565 pw_rpc2: Merge status and handshake into cpp library 3bfb1b8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/504025 pw_bluetooth_sapphire: Own emulator by connection f406e2f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/504047 pw_presubmit: Update lockfile_check to include all lockfiles ad139a4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/502153 pw_rpc2: Add TestHarness unit testing fixture dc10059:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/503487 roll: toolchain-integration 9668db1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501455 pw_transfer: Fix implicit conversion warnings 93c667d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/500734 pw_chrono: Fix implicit conversion warnings d18ca0a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501853 pw_bluetooth_sapphire: Guard against removing connecting peers 2da1f46:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501515 pw_snapshot: Enable implicit conversion warnings a658a8a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501494 pw_trace: Fix implicit conversion warnings 39f9eb2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/501319 pw_ring_buffer: Fix implicit conversion warnings Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 5d3945e5889cc1..efa36ccd68b335 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8667752951078628497 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8ad8132f7b9e0b94abee6b4221a67d76b0c23b1b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/505925
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.