implement gles-alternatives like glx-alternatives

Heiko Stübner heiko at sntech.de
Sat Jul 16 20:26:39 UTC 2011


Hi,

glx-alternatives provides the means to have more than one libGL and glx 
implementation on a machine.

I'm working on the Toshiba AC100 (NVidia Tegra ARM SoC) which also got a 
proprietary driver released two weeks ago [1].

Tegra, like Omap, and probably other SoCs support "only" OpenGL ES (1 and 2) 
wich is also provided by Mesa libs.

So I was wondering what would be the best way to realise a diversion system 
like glx-alternatives for the OpenGL ES stuff.


Possibilities I came up with were:
- build a completely separate gles-alternatives source package realising the 
same functionality like glx-alternatives
- let glx-alternatives also build packages for handling OpenGL ES stuff.

Libs that need to be diverted most of the time are libEGL.so.1, 
libGLESv1_CM.so.1 and libGLESv2.so.2 (at least for Tegra and Omap4[2] ).


Pointers on what way looks saner would be greatly appreciated :-)

Thanks
Heiko

[1] http://tegradeveloper.nvidia.com/tegra/forum/linux-tegra-release-12-
alpha-1-released
[2] http://launchpad.net/~tiomap-dev



More information about the pkg-nvidia-devel mailing list