Google Git
Sign in
pigweed / pigweed / examples / 0179391a9097386f06ba619221d0d349d9bc215e
commit0179391a9097386f06ba619221d0d349d9bc215e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jun 20 20:06:58 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 20 20:06:58 2024 +0000
tree197eeff966d6e6833c51b7aaf1d32a215f1c9380
parent4f864320fd4001cfa304dfe5352a7c72fc400da0 [diff]
roll: third_party/pigweed 10 commits

1d9d180c93b9523 pw_bluetooth_proxy: Add release_fn to H4PacketWith
02532d3875f0244 pw_bluetooth_proxy: Fix case style for some test v
f9f845234c3f536 pw_bluetooth_proxy: Move to-controller flow to usi
da47a16ccccd12f pw_bluetooth_proxy: Add H4PacketWithH4 ctor that t
0d7dfd58bd444d4 pw_bluetooth_proxy: Move H4Packet to using move se
0b2a6a9d699a848 nanopb: Import proto module
27b0e9eeeaffaea bazel: Update TODO in bazelrc
c6e8cd83c4dd6c0 pw_bluetooth_proxy: Fix naming of SetH4Type
325f9a48db05e1c pw_system: Rename target_io.cc
aa9d7a115b06c2f pw_web: Implement responsive toolbar behavior

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: e6c5165547f3054..1d9d180c93b9523
Roller-URL: https://ci.chromium.org/b/8744583413844654545
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I676e5405fd530c9b2920a50c4cc263607f73134b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/217152
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 197eeff966d6e6833c51b7aaf1d32a215f1c9380
  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.