On Wed, Nov 1, 2017 at 10:33 AM, Emil Velikov <[email protected]> wrote:
> On 31 October 2017 at 21:07, Dylan Baker <[email protected]> wrote: > > Quoting Emil Velikov (2017-10-30 10:47:22) > >> On 30 October 2017 at 17:05, Dylan Baker <[email protected]> wrote: > >> > So I think the consensus is this is okay? > >> > > >> > Emil, is the autotools right here? > >> > > >> > >> Without a clear separation or cleanup of the the existing code, this > >> such move brings no technical benefit. > >> If anything, it makes it harder for people [roughly] familiar with > >> current setup. > >> > >> i was wondering if we can nuke wl_drm, but I don't see that happening > >> anytime soon :-( > >> > >> -Emil > > > > How strong is your objection Emil? > > > > My intention is to pull some of the generated files that are shared > > between vulkan/wsi/wayland and egl/wayland/wayland-drm. Daniel has said > that he > > has more generated files that will be shared between them in work he is > doing > > currently, and putting them in neither EGL or Wayland would make the > build > > cleaner, and that's the intention of this series. > > > Across various systems I have over ~10 different branches that cover > egl, gbm and friends. > I have to admit that the goal is very admirable, but it would > seriously hinder attempts to get those sorted. > > If the key issue is wayland-drm - we should be able to move the XML > file to wayland-protocols? > No, wayland-drm is internal to mesa and needs to stay that way. There are other XML files that we need to use which are in wayland-protocols but it would be nice if we had a single place where the codegen is done so we don't have to repeat it per-component.
_______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
