enlightenment/src/modules/conf_theme/meson.build

src = files(
  'e_mod_main.c',
  'e_int_config_borders.c',
  'e_int_config_color_classes.c',
  'e_int_config_fonts.c',
  'e_int_config_scale.c',
  'e_int_config_theme.c',
  'e_int_config_theme_import.c',
  'e_int_config_transitions.c',
  'e_int_config_wallpaper.c',
  'e_int_config_xsettings.c',
  'e_mod_main.h'
 )
meson: use file instead of doing the relative path by hand a reason for doing that is that you can just pack together targets into a array and pass them to our helper, and the helper will just handle them, so even module with eldbus codegen etc is now supported. This also means that we are just passing the src object directly into the shared_module call, which means the user of our helper can just pack everything he needs into the src var and the helper does not need to know about it. 2017-08-08 09:19:11 -07:00			`src = files(`
meosn build modules - more modules build with the generic builder harness module build files are so much simpler now... 2017-07-30 01:03:46 -07:00			`'e_mod_main.c',`
			`'e_int_config_borders.c',`
			`'e_int_config_color_classes.c',`
			`'e_int_config_fonts.c',`
			`'e_int_config_scale.c',`
			`'e_int_config_theme.c',`
			`'e_int_config_theme_import.c',`
			`'e_int_config_transitions.c',`
			`'e_int_config_wallpaper.c',`
			`'e_int_config_xsettings.c',`
			`'e_mod_main.h'`
meson: use file instead of doing the relative path by hand a reason for doing that is that you can just pack together targets into a array and pass them to our helper, and the helper will just handle them, so even module with eldbus codegen etc is now supported. This also means that we are just passing the src object directly into the shared_module call, which means the user of our helper can just pack everything he needs into the src var and the helper does not need to know about it. 2017-08-08 09:19:11 -07:00			`)`