On 24 October 2017 at 02:26, Sharma, Deepak <deepak.sha...@amd.com> wrote: > Hi Emil, > > Is your suggestion is to build mesa in chrome using --with-platforms=drm and > --with-platforms=surfaceless both ? I am not sure if that is required for > chrome. > The approach we are taking here is to build mesa only with > --with-platforms=surfaceless and leverage existing > VA_DISPLAY_DRM* to get VAAPI working on Chrome for platform. > My suggestion is to fix the problem instead of working around it.
> Thus the solution here really is: > - decouple the link-time dependency to a (once-off) runtime one > - and(?) demote the configure error to a warning ;-) Right? > The goal ^^ Note I'm talking about the GBM link-time dependency in EGL. Just use a dlopen(RTLD_LOCAL | RTLD_NOW) /dlsym/dlclose. > While we're there we could/should: > - drop the (first_pointer == gbm_create_device) hack Replace with > dladdr(first_pointer, &info) + strcmp(info.dli_sname, > "gbm_create_device") combo > - make egl_dri2.c free of calls into gbm - only gbm_device_destroy remains > Move the remaining gbm_device_destroy to platform_drm.c > ^^ some implementation suggestions, although you can handle it otherwise. > Bonus points: > - Add ABI and/or version check for Mesa GBM <> EGL interop. > ^^ completely optional, related work. -Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
