Op 30 jul. 2012, om 19:15 heeft "Burton, Ross" <[email protected]> het volgende geschreven:
> Hi, > > I've recently been looking at the Mesa packaging (via the work that > Damien Lespiau has been doing) and am confused as to why there are > both mesa-dri and mesa-xlib packages. I'm also no Mesa expert, so I > thougth I should mail this list... > > The main difference appear to be that mesa-dri uses DRI to render, > whilst mesa-xlib doesn't (so it uses indirect rendering). As DRI > support is hardware specific so surely this could and should be turned > into a FEATURE of some sort, and then let mesa pick appropriately > between DRI or indirect (xlib) rendering. I can't think of a > situation where you'd want to use indirect rendering when you have DRI > available. > > Can anyone see any problems with merging the recipes into a single > "mesa" recipe, and making DRI support conditional on a feature? They produce 2 differently named shared libraries and currently some images need both. If that's a bug or not, I don't know :) regards, Koen _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
