I am trying to use clutter 0.8.8 for an app launcher. In order to get accelerated graphics, some devices require that we use the GLES backend, while others require OpenGL. Since these devices are all the same architecture, I want to be able to compile clutter and build both the gles2 backend and the opengl backend so that we have a packaged version of both. Then when we create the system image, we pick which clutter runtime package to use based on the requirements of the device.
So far so good. However, I suspect this will be a problem for apps using clutter. It seems that the backend in use is not transparent to the app. Even if I change clutter to provide the same library soname with different backends, (conflicting packages of course), at compile time, the backend in use at compile time is required to be the same backend at runtime? Does this mean that I am going to be required to compile/link every clutter using app twice in order to use the required clutter backend on a particular device? -- Stephen Depooter <[email protected]> -- To unsubscribe send a mail to [email protected]
