| commit | 70faf1aa2ca0de3cc8228fc03068e0091b23ee5c | [log] [tgz] |
|---|---|---|
| author | Yuval Peress <peress@pigweed.infra.roller.google.com> | Thu Jan 16 01:13:57 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 16 01:13:57 2025 -0800 |
| tree | a0248e6ed34a24667bb1501a59e02bfb557ae881 | |
| parent | ad15c8cfc26e66e9bfad9b78067cbe9c44ac2da8 [diff] |
roll: third_party/pigweed pw_sensor: Allow missing 'org' in compatible descriptor When providing a sensor descriptor, most will leverage the org,part schema. This does not always seem to be the case. There are times where the org is missing when used in downstream Zephyr. We should allow for this case and only include the org when provided and not empty. BUG=b/386143823 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256773 Original-Revision: fdfca20b13a86610e0d2592c7539d81a93cf9cfe Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 2558be01c41b35..fdfca20b13a866 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8725598186217448161 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I77f6ac42b7ef87951f835cb5e7f846e2c324cd69 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/260596 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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/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.