Google Git
Sign in
pigweed / pigweed / examples / 74f1bb2421ebee45f93c8a7bfce90deb1ed0d3c0
commit74f1bb2421ebee45f93c8a7bfce90deb1ed0d3c0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Jul 13 17:55:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 13 17:55:19 2024 +0000
treee1e36e233e21e265faea11850e5041924f9332d4
parentc2ac22651ff738045724c55b9c1fe46739765a6c [diff]
roll: third_party/pigweed 10 commits

a12f93925d8d184 pw_bluetooth_sapphire: Update LowEnergyAdvertiser
f150ac17e8fde07 pw_bluetooth_sapphire: Add more values to LEEventM
b216eb7fb3a472d pw_bluetooth_sapphire: Pass hci::AdvertisingInterv
505638596e1ea63 pw_bluetooth_sapphire: Shorten pw::bluetooth::embo
071670f2a8e7309 pw_bluetooth_sapphire: Pass extended_pdu booleans
351c9a45b2099b6 pw_bluetooth_sapphire: Update AdvertisingHandleMap
443ea9303c2f1d0 pw_bluetooth_sapphire: Update missing header
de05f2bf9d0c5e9 pw_bluetooth_sapphire: Add the credit-based flow c
c0649cb6ff1798a pw_bluetooth_sapphire: Prevent protected member ac
aab0781bccb8d26 pw_bluetooth_sapphire: Add Bazel tests

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 97bdfeb645a92f7..a12f93925d8d184
Roller-URL: https://ci.chromium.org/b/8742507087479749505
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iceaaa3cf1d5aceeafac77486495cd63777d17498
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/222646
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>
1 file changed
tree: e1e36e233e21e265faea11850e5041924f9332d4
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .bazelignore
  13. .bazelrc
  14. .bazelversion
  15. .gitattributes
  16. .gitignore
  17. .gitmodules
  18. .gn
  19. .pw_console.yaml
  20. activate.bat
  21. banner.txt
  22. bootstrap.bat
  23. bootstrap.sh
  24. BUILD.bazel
  25. BUILD.gn
  26. BUILDCONFIG.gn
  27. LICENSE
  28. navbar.md
  29. OWNERS
  30. pigweed.json
  31. pyproject.toml
  32. README.md
  33. WORKSPACE
README.md

Pigweed Sample Project

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!

Getting started

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

Environment setup

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

Building

All of these commands must be run from inside an activated developer environment. See Environment setup

One-shot build

To build the project, documentation, and tests, run the following command in an activated environment:

pw build

Automatically build on file save

Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:

pw watch

Typical workflow

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

More info and Examples

Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.