expose DBus interface signal names as symbols
Enable a way to access the signal names of a given DBus interface as a
constexpr symbol via the header.
4 use-cases:
- printing error / debug logs with the signal name.
e.g. 'received signal ${SIGNAL_NAME}'
- matching on DBus signals in applications which do not yet use the PDI
generated bindings.
- preventing typos in DBus signal names
- estimating the impact of removing a given DBus signal from an
interface. When using these symbols, it would cause a build failure in
applications relying on the existence of that signal.
This change is similar to [1] and goes into the same direction.
Tested: Newly written unit test passes.
References:
[1] d2571922bfdb4f6b41ba4fbc45b8a4272793fd40
Change-Id: I9c20d744955c883302f349c5351dbdba1753466b
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
diff --git a/test/meson.build b/test/meson.build
index ead3508..5af90c0 100644
--- a/test/meson.build
+++ b/test/meson.build
@@ -125,6 +125,7 @@
'test_aserver_multiple_interfaces',
'test_property_names',
'test_method_names',
+ 'test_signal_names',
]
foreach t : uninit_tests