Is this possible, GNOME (lib)Clutter with OpenGL ES & Vulkane?

386 Views Asked by At

I'm planning to run an app based on (GNOME) libclutter on Android 9 (Pie). I'm quite new to these graphics related stuff, been wondering on these things, so seeking for guidance/direction whatever data that could help me to understand this thing better.

As per the documentation of Android Graphics, Android is using OpenGL ES & Vulkane at low level to render objects. And as per GNOME Clutter documentation, it could be only compiled with mentioned back-end only! (Please check embedded link to for platforms details.)

I don't see OpenGL ES or Vulkane support, So am I missing something on understanding part or it can't be done?!

2

There are 2 best solutions below

4
ebassi On BEST ANSWER

[Clutter maintainer, here]

Yes, Clutter supports OpenGL ES—it uses Cogl, a library that abstracts GL and GLES concepts.

No, Clutter does not support Vulkan at the moment.

No, Clutter and Cogl do not support Android; there was an experimental port but it has been abandoned in 2012.

Additionally, Clutter is in deep maintenance mode: no new development releases, no new features, and only minimal/security/crasher bug fixes are allowed.

I would not recommend using Clutter in a newly written project.

0
Novice On

OKay...after spending few more hours, I was able to figure out an answer! (Yayy..!!!)

As per Clutter Project website: (somehow I had missed this info previously! :p)

Clutter uses OpenGL for rendering (and optionally OpenGL ES for use on mobile and embedded platforms), but wraps an easy to use, efficient, flexible API around GL's complexity.

So, as per my requirement, I should be able to integrate and cross-compile Clutter lib source and compile it.

PS: I will try to integrate & build the libclutter on android 9. Will update this answer latter with additional set of information.

========================================================================== Update: As pointed out by @ebassi in another answer, I have dropped the idea of integration and looking forward to directly using Android Graphics stack for the implementation.

Thanks @ebassi...!