Google Git
Sign in
pigweed / pigweed / examples / eee586d6477a35a2692e88af4ad0b62159cf18ac
commiteee586d6477a35a2692e88af4ad0b62159cf18ac[log] [tgz]
authorJoshua Liebow-Feeser <joshlf@pigweed.infra.roller.google.com>Mon Aug 18 13:13:43 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Aug 18 13:13:43 2025 -0700
tree8ca5dbeb0c9222fec0a4a540f01c7a09968917b3
parentd84a481bc58c86ebd0c5b22c0cb6800705fb91bd [diff]
roll: third_party/pigweed pw_kernel: Remove trait impls on Timer

Remove impls of `[Partial]Eq` and `[Partial]Ord` on `Timer`. Before this
commit, these impls considered two `Timer`s to be equal if their
deadlines were equal, and disregarded their callbacks. If a `Timer` were
inserted into a `HashMap` or similar collection, inserting a `Timer`
with the same deadline as an existing `Timer` would cause the new one to
replace the old one (probably not what the programmer would intend).

Instead, we replace `ForeignList::sorted_insert` with
`sorted_insert_by_key`, which sorts based on a specific field of the
element type. This allows us to insert `Timer`s into `ForeignList`s
by explicitly selecting the `deadline` field as the key.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/313832
Original-Revision: 70a7885506f1d03cbbe0d4e8b6a3965901958f58

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: e6c4f7493b2c8d..70a7885506f1d0
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8706168958490533409
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3a0ac42ceb62e8fbbfe4c121d22c538fc9147218
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/314073
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: 8ca5dbeb0c9222fec0a4a540f01c7a09968917b3
  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. .clang-tidy
  16. .gitattributes
  17. .gitignore
  18. .gitmodules
  19. .gn
  20. .pw_console.yaml
  21. activate.bat
  22. banner.txt
  23. bootstrap.bat
  24. bootstrap.sh
  25. BUILD.bazel
  26. BUILD.gn
  27. BUILDCONFIG.gn
  28. LICENSE
  29. MODULE.bazel
  30. navbar.md
  31. OWNERS
  32. pigweed.json
  33. pyproject.toml
  34. 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.