Hello, On Fri, 16 Jul 2010 07:39:16 -0700, Alan Coopersmith <alan.coopersm...@oracle.com> wrote: > But every app we port ourselves gives us more insight into what is needed > to port apps, and figure out how to make it easier for authors/maintainers > of the much more complicated apps out there in the rest of the world.
Most of "the much more complicated apps" use X through some kind of UI toolkit framework. So I would guess that porting one of those frameworks is what's most "needed to port apps". Keeping in mind that things like GTK, Qt and the likes are intended to *hide* the underlying windowing system, most out there applications do not actually use Xlib directly at all. And then there's the impossible case of GLX :-( Just for the self-centric purely informative reference, the remaining Xlib stumbling blocks in (Lib)VLC are: - GLX, - libSDL, - ASCII Art (don't ask me why libaa needs libX11 ?!), - PulseAudio (libpulse), - Qt4, - VLC's own skin engine, of which only the last item is up to VLC developers to address. -- Rémi Denis-Courmont http://www.remlab.net http://fi.linkedin.com/in/remidenis _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel