| commit | 8be48dda8dc01920c457248a195ac191cd81eec4 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jun 04 18:50:06 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 18:50:06 2024 +0000 |
| tree | 8b9fdd2cbf5d031f75817e22908c2281980e0dad | |
| parent | 434ee128146dd5a0d56df1726f33ea9db83f70e7 [diff] |
[third_party/pigweed] Roll 5 commits 76902e6d4a7fa3c rp2040: Support bazel wildcard build on rp2040 dea891ac18bee92 pw_bluetooth_proxy: Fix compilation errors 5f164749a2bb256 pw_web: Fix last column filling space in log table 9c5ff32b8a7e995 pw_bluetooth_proxy: Pass H4 as event type plus an ee2ddb543cc45ec pw_bluetooth_proxy: Tweak CreateNonInteractingToHo https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 6618a7d3265639b..76902e6d4a7fa3c Roller-URL: https://ci.chromium.org/b/8746036763997250545 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ief4ca9b5624dc44274ca431f74473639fb292d79 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/213931 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.