Was there any conclusion on the idea of "auto" in having the build try to adapt to your systems by default instead of just assuming a configuration? That's the biggest issue I see at the momemt; for many options the current auto-tools build tries to adapt to your system and for the most part does an okay job, the meson build does not.
---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Fri, Nov 23, 2018 at 8:46 PM Marek Olšák <mar...@gmail.com> wrote: > On Fri, Nov 16, 2018 at 11:05 PM Dylan Baker <dy...@pnwbakers.com> wrote: > >> Quoting Dylan Baker (2018-09-17 09:44:07) >> > I feel like for !windows meson is in good enough shape at this point >> that we >> > can start having the discussion about deleting the autotools build. So, >> is there >> > anything left that autotools can do that meson cannot (that we actually >> want to >> > implement)? And, what is a reasonable time-table to remove the >> autotools build? >> > I think we could reasonably remove it as soon as 18.3 if others felt >> confident >> > that it would work for them. >> > >> > Dylan >> >> Okay, time for an update on things and a chance to talk about what else >> we need. >> >> Support for llvm-config (and any binary, actually) overriding has landed >> in >> meson, and will be present in the 0.49.0 release, which is due out >> December 9th. >> support for ICC has improved a great deal already, and I have a series >> here: >> https://github.com/mesonbuild/meson/pull/4359 (which may unfortunately >> not >> land until after 0.49) which should get ICC into pretty good shape on >> Linux and >> Mac, including actually checking that arguments are understood (which >> should >> allow us to drop the prefix test from SWR). I have some ideas on how we >> might >> remove auto options, some of them can already use meson's "feature" >> https://mesonbuild.com/Build-options.html#features option (which should >> make >> distro packagers happy too), for arch and OS specific options I have some >> ideas >> and I'll continue following up with those upstream. >> >> For those interested in llvm-config overriding, with meson out of git you >> can >> add a files like: >> >> $ cat ~/.local/share/meson/native/llvm-6.0 >> [binaries] >> llvm-conifg = '/usr/local/lib/llvm-6/bin/llvm-config' >> >> and invoke meson with: >> meson builddir --native-file llvm-6.0 >> >> which will configure with the specified llvm-config, and remember the >> llvm-config used on subsequent reconfigurations. You can override all >> binaries >> from a native file as well, so if you want to use a specific python3 or >> compiler you can do that, and you can load multiple native files in a >> single >> invocation. >> >> Is there anything else we're missing in meson to be able to drop >> autotools? >> > > Everything seems OK here. > > Marek > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
