| commit | 1e6456766c4a2f70c17b4f8a2f65bd154ca505d6 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Oct 30 21:14:12 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 30 21:14:12 2024 +0000 |
| tree | 29ee1746ff99ebb6a0be806990bcd82a0f6d6aee | |
| parent | 70a071038819e6719dbb9cb6ac9adb9d411a66ef [diff] |
roll: third_party/pigweed b22815d..9ab6e74 (5 commits) 9ab6e74:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/245132 pw_multibuf: Add FromSpan 9ee6af1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/245448 pw_bluetooth_hci: Add Android.bp 3824b3a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/245115 docs: Configure docs toolchain to have large flash & ram ff34b8b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/244534 docs: Use pw_assert_tokenized in docs toolchain 482df43:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/242473 pw_protobuf_compiler: Make oneof callbacks default in Bazel Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: b22815d8fe704f..9ab6e749821edd Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8732619451595193153 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9e53e79e5670a3acc78125f682b492c634dfb9c9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/245573 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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/sample_project/+/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/sample_project
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.