| commit | cc7c25504c6e002783bfa6c0718f8b1ab1514e9c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Aug 29 01:41:40 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 29 01:41:40 2024 +0000 |
| tree | 9ac7bf3d4cf70216b7b2bf58c60bcaead7e3ce3f | |
| parent | e31eb9e10fcf03d4cb6d3bb59d551dfb40cb8659 [diff] |
roll: third_party/pigweed: pw_bluetooth_sapphire: Use select() for Fuchsia-only values in Bazel Avoid using fuchsia_select in Pigweed because the Fuchsia code in Pigweed is being refactored into its own Bazel module. Original-Bug: b/357895400 Test: fx build Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1099247 GitOrigin-RevId: 9f88c078cd90d205e55d234bb0d2c584d46960ca Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/230578 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 102a0f6737990f7..a3a5a3421efd155 Roller-URL: https://ci.chromium.org/b/8738310140361130145 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8627a6c5657722c3b5c55613e1b84d816efa1c68 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/232542 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.