Hi Carsten, On 2014-07-25 1:07 PM, Carsten Haitzler wrote:
>>> Mesa could also be used during build time instead of the >>> opegl-es-virtual-drv. >> Yes and no, I think. There is the minor problem that the Mesa >> drivers provide a versioned libGLESv2.so.2, which all of the >> built packages will link to. This means that if I want to >> install a driver (such as Mali or SGX) after the fact, I have to >> provide libGLESv2.so.2 to overwrite the Mesa driver. If Mesa >> changes its version number for some reason, now the Mali and SGX >> drivers must update their names as well. opegl-es-virtual-drv is >> nice because it is not versioned, so as long as there is a >> libGLESv2.so (or a link of that name) in the non floss drivers, >> everything works. > > or just provide a symlink. far simpler a solution. drivers just > ghave to agree all to provide at least the same symlink to the real > driver version > I don't think it matters whether it's a symlink or not. Either way, it requires all of the drivers to keep track of whatever version number that Mesa is using for its libGLESv2 and update the symlink accordingly. Damian _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
