Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 2f3794fb151e58cc84f3bf6ff890a37f5cb60ab2
commit2f3794fb151e58cc84f3bf6ff890a37f5cb60ab2[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Wed Feb 05 16:21:19 2025 -0500
committerJayanth Othayoth <ojayanth@gmail.com>Wed Feb 05 22:33:16 2025 -0600
tree4636fd51d09b6dc29ad498fbf02bcd990ca3bba9
parent03414ffa629d290c16d9561d780d140fa1f0ccfa [diff]
dump_types: change filenames to [ch]pp.mako

We have a tendency to name mako files as "foo.type.mako" rather than
"foo.mako.type" because too many tools tend to identify the file as a
"type file" rather than a "mako file".  Right now, meson is somehow
picking up these files as part of the `clang-tidy` invocation and
puking on it.  Rename the files both to fit convention and to avoid
the issues.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I65a80860242f7d8841b5d3a18d9847d87d087eb8
3 files changed
tree: 4636fd51d09b6dc29ad498fbf02bcd990ca3bba9
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. .clang-format
  7. .clang-tidy
  8. .gitignore
  9. .shellcheck-ignore
  10. bmc_dump_entry.cpp
  11. bmc_dump_entry.hpp
  12. core_manager.cpp
  13. core_manager.hpp
  14. core_manager_main.cpp
  15. dump-extensions.hpp
  16. dump_entry.cpp
  17. dump_entry.hpp
  18. dump_manager.cpp
  19. dump_manager.hpp
  20. dump_manager_bmc.cpp
  21. dump_manager_bmc.hpp
  22. dump_manager_faultlog.cpp
  23. dump_manager_faultlog.hpp
  24. dump_manager_main.cpp
  25. dump_offload.cpp
  26. dump_offload.hpp
  27. dump_serialize.cpp
  28. dump_serialize.hpp
  29. dump_types.cpp.mako
  30. dump_types.hpp.mako
  31. dump_utils.cpp
  32. dump_utils.hpp
  33. elog_watch.cpp
  34. elog_watch.hpp
  35. example_dump_types.yaml
  36. example_errors_watch.yaml
  37. faultlog_dump_entry.cpp
  38. faultlog_dump_entry.hpp
  39. ffdc
  40. host_transport_exts.hpp
  41. LICENSE
  42. map_gen.py
  43. meson.build
  44. meson.options
  45. OWNERS
  46. ramoops_manager.cpp
  47. ramoops_manager.hpp
  48. ramoops_manager_main.cpp
  49. README.md
  50. watch.cpp
  51. watch.hpp
README.md

phosphor-debug-collector

Phosphor Debug Collector provides mechanisms to collect various log files and system parameters. Used to troubleshoot problems in OpenBMC based systems.

One such mechanism is dreport, a script that collects debug data and packages it into an archive file.

To Build

To build this package with meson, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To clean the built files run ninja -C builddir clean.

To run unit tests

Tests can be run in the CI docker container, refer local-ci-build

or with an OpenBMC x86 sdk(see below for x86 steps).

meson -Dtests=enabled build
ninja -C build test