| commit | 806582c670c89f6ba9808c5522311b48df593e8c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Feb 05 15:13:18 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 05 15:13:18 2025 -0800 |
| tree | 166ad51f232b32e3b945ff2076dd32a9a1f2beae | |
| parent | 947dc2cddf8ac31b199710dcfefbaa1da73696fd [diff] |
roll: third_party/pigweed d95bb92..fac44b1 (3 commits) fac44b1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264912 build: Propagate Rust channel to proc macros (exec cfg) 89a3c9c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264954 pw_bluetooth_proxy: Support acquire of gatt notify channels 6e18552:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265212 pw_bluetooth_proxy: Use explicit constructor for std::atomic Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: d95bb9205b6826..fac44b1dc4f107 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8723733442097721713 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Icb6fc369664eb384c777160f74255dd8092429e5 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/265116 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.