commit | 16b6620450e7e20b8393001f568c9140d7e24f7d | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Dec 20 13:44:47 2024 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 20 13:44:47 2024 -0800 |
tree | 54e774e89f3fc0cc241547db99800bc79aaf7718 | |
parent | c13a7f16b6e2614d9443db4e9f90c1113332c0d5 [diff] |
roll: third_party/pigweed c13d91e..37845ac (9 commits) 37845ac:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256114 pw_bluetooth_proxy: Fix ubsan finding in L2capCoc d69cd4a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255970 pw_bluetooth_proxy: Fix wrong cid lookup on l2cap disconnect 982b225:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256172 pw_bluetooth_sapphire: Don't lose pairing delegate during connection 983119e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255968 pw_bluetooth_proxy: Remove incorrect field comment 49ca810:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256132 pw_bluetooth: Define Poll/Final variants in RfcommFrameType enum 330670b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/256152 pw_bluetooth_proxy: Initialize arrays d78f076:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255964 pw_tokenizer: Fix undefined return values in TS 5356fe8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/253515 pw_thread: Remove unnecessary thread_core.h include and dep 17c85f7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255963 pw_hdlc: Remove/rename PW_RPC_MAX_PACKET_SIZE Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: c13d91eae61a50..37845ac8c632b2 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8727997121990842017 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6639fae62319b55a09852632fea955ec2d8fd57e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/256232 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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
.