I have no idea if anyone has ever tried this, it may work, it may not - only real way to know would be to try. MiniGLX seems like a bit of a hack - I've no idea if it even works itself.
Alternatively, afaik, directfb supports GL on frame buffer. It shouldn't be too hard to create a directfb backend for clutter. That may be a safer option. == Matthew On Sun, 2008-05-18 at 21:30 +0200, Simon Prückl wrote: > Heyho, > > I want to use Clutter without an X-Server by using the fbdev/DRI > environment from the mesa3d-project. > This fbdev/DRI environment provides the so called miniGLX. MiniGLX is > a specification implementing OpenGL without an X-Server. > (http://mesa3d.org/MiniGLX.html) > > MiniGLX has a few technical restrictions as mentioned here: > http://mesa3d.org/MiniGLX.html > > > 4.0 Interoperability with GLX and Xlib > While Mini GLX strives to be compatible with GLX and Xlib there are > some unavoidable differences which must be taken into consideration. > 4.1 Public vs Private Structures > The structure of many X data types is public. For example, the > Display data type is defined as a structure in /usr/include/X11/Xlib.h > and programmers may access any fields of that structure at will. Mini > GLX also defines a Display data type but its fields are hidden and not > visiblein miniglx.h. Duplicating the Xlib declaration for the Display > > Mini GLX users are discouraged from directly accessing the fields of > Xlib data types to maximize portability - though this is unavoidable > to some extent. For example, the XVisualInfo and > XSetWindowAtttributes data types must be completely public. data type > in minigl.h would require defining a large number of other superfluous > Xlib datatypes. > 4.2 Macros > In some cases, Xlib defines macros which are meant to be used instead > of direct structure accesses. For example, the RootWindow(dpy, > screen) macro returns the root window for a given screen on a given > display. Unfortunately, macros do nothing to aid in ABI compatibility > since they are resolved at compile time instead of at link/run time. > > Mini GLX also defines a RootWindow macro since it's essential for > creating windows. But the implementation of this macro by Xlib and > Mini GLX is completely different. > > 4.3 Summary > Because Xlib and Mini GLX define data types and macros differently, > Mini GLX applications must be recompiled when retargeting Mini GLX or > native Xlib/GLX. That is, applications can't simply be re-linked > because of ABI incompatibilities. > > Nevertheless, the fact that Mini GLX programs can be recompiled for > Xlib and GLX increases portability and flexibility for testing and > prototyping. > > > > It would be great if you could tell us, whether clutter can be used > via MiniGLX and whether those restrictions affect the clutter-toolkit. > If you're interested in this fbdev/DRI project, have a look at > http://mesa3d.org/fbdev-dri.html . > > Is it possible to you clutter with MiniGLX? has anyone ever tried? > Would be great if you could help us - thanks in advance, > > regards, > Simon Prückl -- To unsubscribe send a mail to [EMAIL PROTECTED]
