We don't attempt to explicitly explain what a specific "virtual/something" actually provides. In most cases this is fairly obvious but especially around OpenGL this is not so. We should try and document some of them The ones that I think should have an explanation, and some guesses to start with: * virtual/mesa Provides gbm.pc <- no idea where we expect this to come with really ??? * virtual/egl: Provides egl.pc and _possibly_ wayland-egl.pc <- I guess ??? * virtual/libgl: Provides gl.pc (meaning libGL) * virtual/libgles1 Provides glesv1_cm.pc (meaning libGLESv1_CM) * virtual/libgles2 Provides glesv2.pc (meaning libGLESv2) Another question: Should we add "virtual/gbm" or ask TI folks to do it if they think their fork is compatible enough?
Assigning to Kristi. Set Person days. Scott
Creating a new section.
I've created a new "Metadata (Virtual Providers)" section to the ref-manual for review here: http://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#metadata-virtual-providers Please take a look at the concept paragraph, and bulleted list. I essentially copied the list provided, so please provide additional detail as necessary and I will update. Additionally, if there are others to explain, let me know and I will update the list. Thanks! Kristi
Richard, Please review and comment.
This issue is done... see https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#metadata-virtual-providers. Setting to RESOLVED and putting the Doc flag to "Done" Scott