| commit | 786fe83f8f177732a67cf9b8e571767519d7e905 | [log] [tgz] |
|---|---|---|
| author | Stephanie DiBenedetto <dibenede@pigweed.infra.roller.google.com> | Mon Apr 07 19:12:50 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 07 19:12:50 2025 -0700 |
| tree | 40c9e315fe747b65aae25323e226c868a75c53b5 | |
| parent | 2511a63c14877400a9091e1017a8853fc5f37aaa [diff] |
roll: third_party/pigweed pw_transfer: Add Number() coercion for 64-bit int proto field access The internal JSPB implementation is migrating 64-bit int fields to a new bigint|string type. This change adds a defensive coercion to ensure the value remains number-typed. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281833 Original-Revision: 64d06ced56dd4dfa435541a10fd157b621e22673 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 2452fa9903c157..64d06ced56dd4d Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8718195679012882337 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5312f560ed6da908b562ff8ca2d4d3d72b0eb860 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/282072 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.