commit | 46a0764ae6605175368ded5c53b4f5f654cd782c | [log] [tgz] |
---|---|---|
author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Thu Jan 16 16:12:52 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 16 16:12:52 2025 -0800 |
tree | 5b39c1b51942dfa13abe4ca24cca1277dcc4069b | |
parent | 890681225c1511866e1e58aa8d35556ec3f656e4 [diff] |
roll: third_party/pigweed pw_rpc: Revert Java client call ID changes This reverts four changes related to the pw_rpc Java client: 16c4b6397 pw_rpc: Update soong dependencies for java fec7e1118 pw_rpc: Introduce Client.createLegacySingleCall to simplify migration c2de65834 pw_rpc: Temporarily ignore call IDs by default in Java client 15d4ae5ff pw_rpc: Increment call_ids for java client Some users reported RPC timeouts with these changes. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/260892 Original-Revision: 0afdf903105c46e8572591de16b7fd2964ad0874 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 35a7f794be7960..0afdf903105c46 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8725541673460796081 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id48e1c850d705e18c30985926be93b021f76cba9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/260952 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
.