wireplumber/tests
George Kiagiadakis 8a8cd97ca8 core: make the object registration functions public
This allows registering arbitrary objects on the core's registry and
finding them later, without having to add API for each and every object.

I think this is useful enough to have it public, even though it's
probably not going to be used that much... The rationale here is to
allow registering custom component loaders without having to make them
subclass WpPlugin or to create custom API for registering component
loaders specifically.

Also, remove the wp_plugin_register() and wp_si_factory_register()
functions, since they are not going to be used much in the future.
The idea is to let the component loader do the registration under the
scenes, as the component is getting loaded.
2023-06-20 12:39:29 +03:00
..
common log: rename "message" level to "notice" and print criticals with "E" 2023-05-18 16:19:49 +03:00
examples core: change the component arguments to be WpSpaJson instead of GVariant 2023-05-25 18:29:58 +03:00
modules core: introduce the notion of provided features on components 2023-06-20 12:39:29 +03:00
scripts default-nodes-tests: use the changed variable in test utils 2023-04-17 07:48:18 -04:00
wp dbus: refactor WpDBus into a plugin called dbus-connection 2023-06-20 12:39:29 +03:00
wplua log: implement a log topics system, like pipewire 2023-05-16 20:42:28 +03:00
meson.build tests: run with WIREPLUMBER_DEBUG=T, not 7... 2023-05-19 21:13:19 +03:00
script-tester.c core: make the object registration functions public 2023-06-20 12:39:29 +03:00