roll: third_party/pigweed d536942..a562484 (8 commits) a562484:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/372292 pw_memory: Change pw_memory to cc_library_static in Android.bp d01bd7a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/372693 pw_containers: Remove InlineAsyncQueue and InlineAsyncDeque a5256bb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/372692 pw_channel: Remove packet proxy fd0e4be:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/372652 pw_bluetooth_proxy: Remove comms2 code 4a8c1d1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/369813 pw_tokenizer: Accept extra databases 9117cc2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/372432 pw_multibuf: Add checks for MultiBuf move-assignment 6036f00:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/370520 pw_allocator: Refactor shared pointer constructors and casts 098dc71:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/370012 pw_build: Cleanup and test coverage for pw_pylint.bzl Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: d536942055e0cf..a562484df342cf Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8690573845674730193 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I37f31d747a2c559bedf6b80b21a70a4fd01f95e2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/372832
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.