Google Git
Sign in
pigweed / pigweed / examples / 329f857b716e01000d8ea47fc7c58881b8c19a10
commit329f857b716e01000d8ea47fc7c58881b8c19a10[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Sep 08 21:53:03 2023 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Sep 08 21:53:03 2023 +0000
tree51de16159d396e9822edc2befcbbe800ffe36a76
parentc588dc43cc6f7fce46885ea1a901b102ce9b73b2 [diff]
[roll third_party/pigweed] pw_bluetooth: Add UserPasskeyNotificationEvent Emboss definition

Test: pw presubmit --step gn_emboss_nanopb_build
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/169917

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f0da6aa28012b48..6d6d5173af21984
Roller-URL: https://ci.chromium.org/b/8770486412337868321
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I416f528dfa0bce09d057b0bc3840f8a7a7906dd4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/sample_project/+/169867
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 51de16159d396e9822edc2befcbbe800ffe36a76
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. source/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .gitattributes
  13. .gitignore
  14. .gitmodules
  15. .gn
  16. activate.bat
  17. banner.txt
  18. bootstrap.bat
  19. bootstrap.sh
  20. BUILD.gn
  21. BUILDCONFIG.gn
  22. LICENSE
  23. navbar.md
  24. OWNERS
  25. pigweed.json
  26. pyproject.toml
  27. README.md
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. Once that is done, you can clone this project and all required git submodules with the following command:

git clone --recursive https://pigweed.googlesource.com/pigweed/sample_project

If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.

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/docs/gen/docs/html/index.html.