Google Git
Sign in
pigweed / pigweed / examples / f90553fb6d1ada624bd65dbbd8bb16ac093f7c9f
commitf90553fb6d1ada624bd65dbbd8bb16ac093f7c9f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Feb 13 17:49:53 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 13 17:49:53 2025 -0800
treef0020dff146df25b4dcb385a434a19aeeee0ee2e
parenta7aa6fbb37e60a5cb4037bb503d28970b6fc8f4c [diff]
roll: third_party/pigweed e1d73a0..0481c3f (8 commits)

0481c3f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267215 pw_ide: Natively process compDBs in VS Code
4b8b525:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267572 pw_bluetooth_sapphire: Wait for LE Pairing in SSP
3fc29bc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264637 pw_allocator: Add size reports for blocks
4fc31df:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266040 pw_bluetooth_sapphire: Handle BR/EDR CTKD in SM after connection
2e41749:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267932 pw_kernel: Make optimized build the default
335316a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267335 pw_build: Add pw_py_importable_runfile
d1c3488:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267793 CMake: Set policy to silence warnings; make minimum versions consistent
04fb4db:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/262853 pw_log_null: Prevent asserts being routed to pw_log_null

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: e1d73a02c47f07..0481c3fccfd309
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8722998853302913377
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I65615c449579ecd117a0dc0f29a34d50c7ce94ec
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/267856
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>
1 file changed
tree: f0020dff146df25b4dcb385a434a19aeeee0ee2e
  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. MODULE.bazel
  29. navbar.md
  30. OWNERS
  31. pigweed.json
  32. pyproject.toml
  33. 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.

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.