Google Git
Sign in
pigweed / pigweed / examples / 42aadd9e81dd82651faa05d72799e152c4eaf220
commit42aadd9e81dd82651faa05d72799e152c4eaf220[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Feb 20 14:30:35 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 20 14:30:35 2025 -0800
treeed2ce2f7898564a6344b666a2767ae26c0f2da59
parent408606478e623a6e5a5e51377817cff106e0cf8c [diff]
roll: third_party/pigweed 94391ef..0c58d27 (9 commits)

0c58d27:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/268732 pw_multibuf: Add support for alignment to SimpleAllocator
71f9739:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264514 pw_env_setup: Remove bazel.json
e114a96:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/269393 pw_presubmit: Update .clang-format to add newlines at the end of files
0012099:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/268952 pw_bluetooth_proxy: Support two word event callback functions
4cbbd18:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/269592 pw_ide: Unify testing
d41e457:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/269052 pw_kernel: Dump exception frame on every exception
73977b9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267992 pw_kernel: Add NVIC register accessors
73c1156:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267935 pw_kernel: Add systick register definitions
36e8e0a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267934 pw_kernel: Add thumbv8m MPU register definitions

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 94391ef6c7db8a..0c58d27272243d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8722377259975620529
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I43862d3f233fd76765194cbe44387738636ea566
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/269772
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: ed2ce2f7898564a6344b666a2767ae26c0f2da59
  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.