roll: fixes needed to roll pigweed forward

The Pigweed update (rolling to
pigweed@084a8865ef4d9219b558d1945b8dbc0010a95ba2) introduced a schema change
in the pw_kernel system configuration files ( system.json5 ):

1. The  threads  field was removed from the  ProcessConfig  schema.
2. Threads must now be defined as objects of  type: "thread"  inside
   the  objects  list of a process.
3. Additionally, the upstream  test_interrupt_listener  test now
   expects a wait group named  interrupt_wait_group  to be present in the
   configuration.

Signed-off-by: Chris Frantz <cfrantz@google.com>
14 files changed
tree: 7f7767088d730dd05f43dc64cffd3fefb48158d9
  1. .github/
  2. docs/
  3. drivers/
  4. hal/
  5. openprot/
  6. platform/
  7. presubmit/
  8. services/
  9. target/
  10. third_party/
  11. tools/
  12. util/
  13. .bazelignore
  14. .bazelrc
  15. .bazelversion
  16. .clang-format
  17. .gitignore
  18. .semgrepignore
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. pw
  25. README.md
  26. rust-toolchain.toml
  27. workflows.json
README.md

OpenPRoT

Technical Charter

The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md

Getting Started

NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.

Available Tasks

You can run tasks using the Pigweed workflow launcher pw or bazel.

  • ./pw presubmit - Run presubmit checks: formatting, license checks, C/C++ header checks and clippy.
  • ./pw format - Run the code formatters.
  • bazel test //... - Run all tests.
  • bazel build //docs - Build documentation.

Development

The project is structured as a bazel module.

Requirements

  • Bazel. We recommend installing bazelisk to automatically manage bazel versions.

No additional tools are required - all dependencies are managed by bazel.