enlightenment/src/modules/conf_bindings/meson.build

src = files(
  'e_mod_main.c',
  'e_int_config_acpibindings.c',
  'e_int_config_edgebindings.c',
  'e_int_config_keybindings.c',
  'e_int_config_mousebindings.c',
  'e_int_config_signalbindings.c',
  'e_int_config_swipebindings.c',
  'e_mod_main.h'
)

desktop_only = true
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_acpibindings.c',`
			`'e_int_config_edgebindings.c',`
			`'e_int_config_keybindings.c',`
			`'e_int_config_mousebindings.c',`
			`'e_int_config_signalbindings.c',`
Introduce gesture recognition This is currently using libinputs gesture recognition. And offers a config screen to setup new gestures. 1. No default gesture bindings are setup 2. When libinput is not available the module is not going to be loaded, and nothing is recognited.+ 3. Only swipe gestures are recognized yet. 4. For now, you are required to be part of the input group, otherwise we cannot get the libinput events. (See Todo 1) 5. The visual representation is not really good. In terms of UI, it is visually showing a value coming from left to right, which is indicating a direction, which is not always the direction of the gesture, which is kind of bad. More improvements needed here. Some things that still can be done: 1. The whole libinput things should be handled by elput, either with the input group hack, or logind, or simply by root. The ideal idea would be that e_sys is creating the elput context, which also listens for new devices etc.. When all this is done, and it recognizes a new device, it can simply sent a message from e_sys to e, that there is some new device, with a opened fd. (However, this all needs to be locked up in a way that e_sys cannot be abused) 2020-07-02 03:18:42 -07:00			`'e_int_config_swipebindings.c',`
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.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			`)`
meson. 2017-07-21 13:20:03 -07:00
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			`desktop_only = true`