roll: third_party/pigweed pw_async2: Add initial Soong support - Add Android.bp file to build dispatcher used by Pigweed BT modules. - Replace PW_DCHECK with PW_CHECK in statement to avoid unnecessary fallthrough. NO_IFTTT=updating build scripts not in IFTTT. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/359473 Copybara-Verified: Copybara Prod <copybara-worker-blackhole@google.com> Original-Revision: 165ac53ebd67c0f80308b3e6ec1e494e76c1d47f Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: e7cd04d8bad54c..165ac53ebd67c0 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8694001635297080737 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I338594d73d8d47359a44b4e2797050d8d2d9f7fe Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/359853 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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/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.