Julian Bouzas c61d1e4245 component-loader: make wp_core_load_component() API asynchronous ... This change completely refactors the way components are loaded in wireplumber: - The module_init() function must return a GObject now. This object is either a WpPlugin or a WpSiFactory in the current modules. - When the component loader initializes a module, it automatically registers the WpPlugin or WpSiFactory with their respective methods. There is no need to register the WpPlugin or WpSiFactory in the module now. - The wp_core_load_component() API has been refactored to be asynchronows. This allows the component loader to automatically activate WpPlugin objects, and therefore allows the application to directly get the WpPlugin without having to find it. This simplifies a lot of things. - The 'ifexists' and 'nofail' component flags now work even if the respective WpPlugin could not be activated. - The code that loads components in main.c has also been simplified a lot, and the option to load dangling components has also been removed.		2023-04-17 07:48:18 -04:00
..
common	tests: Add tests for WpSettings object	2023-04-17 07:44:19 -04:00
examples	tests: remove audiotestsrc-play example	2023-04-17 07:48:18 -04:00
modules	component-loader: make wp_core_load_component() API asynchronous	2023-04-17 07:48:18 -04:00
scripts	m-metadata: remove module-metadata and replace it with a simple lua script	2023-04-17 07:48:18 -04:00
wp	lib: remove WpEndpoint and WpSiEndpoint APIs	2023-04-17 07:48:18 -04:00
wplua	tests: use WpConf for the settings unit tests	2023-04-17 07:48:18 -04:00
meson.build	tests: remove audiotestsrc-play example	2023-04-17 07:48:18 -04:00
script-tester.c	component-loader: make wp_core_load_component() API asynchronous	2023-04-17 07:48:18 -04:00