Right now the Motorcar example client is a single monolithic file more than 1k lines long. The goal here is to pull all the boilerplate code into a shared library (built as part of the motorcar core, like the motorcar compositor library) and have the application only be code for application specific things (like drawing content and handling events). The shared library will expose an api similar to something like glut or glfw, but for 3D windowing.
This issue depends on breaking the qtwayland dependency as that will involve refactoring the compositor library build system to use cmake instead of qmake, and that will allow the client library build system to use cmake as well.
Actually, this doesnt depend on the resolution of issue #9 in its entirety, only on the move to cmake. Maybe we should have a separate issue to track this.
Right now the Motorcar example client is a single monolithic file more than 1k lines long. The goal here is to pull all the boilerplate code into a shared library (built as part of the motorcar core, like the motorcar compositor library) and have the application only be code for application specific things (like drawing content and handling events). The shared library will expose an api similar to something like glut or glfw, but for 3D windowing.
This issue depends on breaking the qtwayland dependency as that will involve refactoring the compositor library build system to use cmake instead of qmake, and that will allow the client library build system to use cmake as well.