| commit | c5cb769e990f9fe43c95325843a570195d8b7ea7 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 04 16:23:03 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 04 16:23:03 2025 -0700 |
| tree | d2f27d3701e96080da98511ba2fdd2b613381865 | |
| parent | fc2c700c7eabc00dc598d8edceaceea0873f7c0c [diff] |
roll: third_party/pigweed b6ba89f..90d1391 (11 commits) 90d1391:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281383 mbedtls: Remove `-fno-lto` from config 284af91:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281278 pw_kernel: Support Rust ABI thread entry points d780738:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280836 pw_bluetooth_sapphire: Acquire wake leases in CommandChannel 5e3fd74:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278013 pw_bluetooth_sapphire: Acquire wake leases in l2cap::ChannelImpl d91e37c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277233 pw_kernel: Implement syscalls 143289f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281452 pw_tokenizer: Move test out of pw::tokenizer to reflect real use 7ce7812:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281279 bazel: Explicitly specify platforms for crates_std 7a7e380:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281374 pw_kernel: Thread entrypoints are `extern "C" fn`s 0478608:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280977 pw_kernel: Add optional Mutex debug logging 26e657b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/269613 LTO: Retain symbols that were discarded by LTO 58e290a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/245173 pw_tokenizer: Clarify tokenization in headers Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: b6ba89f7c4a12b..90d1391ff0c2fc Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8718478207668514097 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4ecb0ee6cfb818262314ad9d7c19da86762cd3e9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/281433 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.