libmks/tools/meson.build

tools = {
  'mks-connect': {},
  'mks': {},
}

foreach tool, params: tools
  tool_exe = executable(tool, '@0@.c'.format(tool),
    dependencies: libmks_dep,
         install: get_option('install-tools'),
  )
endforeach
initial commit This library doesn't do much yet. It contains the scaffolding and the rough shape of what I think the API should be in mks-types.h. Some of the types have some skeleton implementation as well to hid the D-Bus API behind those types. The next steps are to fill out the other wrapper objects and see what properties we should expose from the underlying D-Bus proxies. Along with that, will be a GtkWidget which can have a number of properties set on it to specify the MksScreen, MksKeyboard, and MksMouse devices. It may make sense to attach the session + screen to the widget, so that it can adapt to keyboard and mouse changes though. 2023-02-08 18:06:08 -08:00			`tools = {`
			`'mks-connect': {},`
tools: add mks tool for testing Mostly so I can test the paintable implementation as I go. 2023-02-10 16:30:23 -08:00			`'mks': {},`
initial commit This library doesn't do much yet. It contains the scaffolding and the rough shape of what I think the API should be in mks-types.h. Some of the types have some skeleton implementation as well to hid the D-Bus API behind those types. The next steps are to fill out the other wrapper objects and see what properties we should expose from the underlying D-Bus proxies. Along with that, will be a GtkWidget which can have a number of properties set on it to specify the MksScreen, MksKeyboard, and MksMouse devices. It may make sense to attach the session + screen to the widget, so that it can adapt to keyboard and mouse changes though. 2023-02-08 18:06:08 -08:00			`}`

			`foreach tool, params: tools`
			`tool_exe = executable(tool, '@0@.c'.format(tool),`
			`dependencies: libmks_dep,`
build: allow installing tools for testing 2023-02-17 16:27:21 -08:00			`install: get_option('install-tools'),`
initial commit This library doesn't do much yet. It contains the scaffolding and the rough shape of what I think the API should be in mks-types.h. Some of the types have some skeleton implementation as well to hid the D-Bus API behind those types. The next steps are to fill out the other wrapper objects and see what properties we should expose from the underlying D-Bus proxies. Along with that, will be a GtkWidget which can have a number of properties set on it to specify the MksScreen, MksKeyboard, and MksMouse devices. It may make sense to attach the session + screen to the widget, so that it can adapt to keyboard and mouse changes though. 2023-02-08 18:06:08 -08:00			`)`
tools: add mks tool for testing Mostly so I can test the paintable implementation as I go. 2023-02-10 16:30:23 -08:00			`endforeach`