On Mon, 2018-12-03 at 16:17 -0800, Dylan Baker wrote: > Quoting Bas Nieuwenhuizen (2018-12-03 14:14:19) > > On Mon, Dec 3, 2018 at 7:30 PM Jan Vesely <jan.ves...@rutgers.edu> wrote: > > > On Mon, 2018-12-03 at 10:21 +0000, Eric Engestrom wrote: > > > > Cc: Emil Velikov <emil.l.veli...@gmail.com> > > > > Cc: Andres Gomez <ago...@igalia.com> > > > > Cc: Juan A. Suarez Romero <jasua...@igalia.com> > > > > Cc: Dylan Baker <dy...@pnwbakers.com> > > > > Signed-off-by: Eric Engestrom <eric.engest...@intel.com> > > > > --- > > > > This patch depends on the releasing procedure in docs/releasing.html to > > > > be updated to not rely on autotools anymore. > > > > > > > > I think our release managers (cc'ed) should work together and figure out > > > > the procedure they want to go by; only once that's done can we delete > > > > these 200+ files and 14k+ lines :) > > > > > > once again, I'm going to request that this patch is delayed until meson > > > 0.49 is more widely available (it has not been released yet!). > > > afaik, there is currently no way to build against non-default llvm > > > outside autotools. > > > > Can't you just add the llvm-config of the non-default to the PATH (and > > if you have a setup which instead of putting it in a different path > > suffixes it, make a new directory, add a llvm-config symlink in there > > and add that to the PATH)? I've been building with non-default llvm > > for ages with meson.
It works as a backstop for scripted updates. The problem is that the next rebuild will silently switch to system default llvm, so I'd need to set the PATH before every ninja call. > You can, that's what I've done as well. 0.49 just has a much nicer mechanism > (and one that presumably distro packagers can use more easily). I don't understand why distros are such a big focus. Don't they all have scripts to build packages? Why would volatility of configuration options be a problem for them? Then again I'm not a distro maintainer ... Jan > > Dylan > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev
signature.asc
Description: This is a digitally signed message part
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
