Message ID | 6c6c678af9a7ff235f32d25f3bea03670749f41d.1397750571.git.yann.morin.1998@free.fr |
---|---|
State | Accepted |
Headers | show |
Dear Yann E. MORIN, On Thu, 17 Apr 2014 18:04:23 +0200, Yann E. MORIN wrote: > config BR2_PACKAGE_MESA3D_DRI_DRIVER > select BR2_PACKAGE_MESA3D_DRIVER > + select BR2_PACKAGE_HAS_LIBGL > bool > > +config BR2_PACKAGE_PROVIDES_LIBGL > + default "mesa3d" if BR2_PACKAGE_MESA3D_DRI_DRIVER I find this a little bit confusing. Wouldn't it make more sense to have a BR2_PACKAGE_MESA3D_GL option, that gets automatically defined when mesa3d provides a full OpenGL implementation? I know it appears to technically be the same as Mesa3D having a DRI driver, but it would look more logical. In fact, the Mesa3D situation is so complex that a good fat comment on top of its Config.in file may be useful to have :) Thomas
diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in index bd7a853..0793b48 100644 --- a/package/mesa3d/Config.in +++ b/package/mesa3d/Config.in @@ -26,8 +26,12 @@ config BR2_PACKAGE_MESA3D_GALLIUM_DRIVER config BR2_PACKAGE_MESA3D_DRI_DRIVER select BR2_PACKAGE_MESA3D_DRIVER + select BR2_PACKAGE_HAS_LIBGL bool +config BR2_PACKAGE_PROVIDES_LIBGL + default "mesa3d" if BR2_PACKAGE_MESA3D_DRI_DRIVER + config BR2_PACKAGE_MESA3D_DRIVER bool