[Mesa-dev] last call for autotools

Dylan Baker dylan at pnwbakers.com
Fri Dec 14 23:38:00 UTC 2018


Quoting Dave Airlie (2018-12-14 12:27:35)
> On Fri, 14 Dec 2018 at 16:19, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> >
> > I have to say that the user experience for autotools is WAY better
> > than for meson. As a concrete example, I had a meson build. Then I
> > updated meson (0.48.1 to 0.48.2). Now ninja -C foo doesn't work. meson
> > --reconfigure (which presumably is what ninja would end up running)
> > doesn't work. http://paste.debian.net/hidden/cf777f3e/
> >
> > So now what? I don't remember how that config was done, except that it
> > was done the way I decided I needed it at the time. I have no way to
> > recover it. With autotools, in such cases (which are immensely rare),
> > you just run "head config.log" and it tells you what you did last
> > time. And by updating the build component, now I have to rebuild
> > EVERYTHING?
> >
> > meson is not at a point where it Just Works. It ... sometimes works.
> > The fact that everyone has scripts which wrap meson is a symptom of
> > that. I don't feel good about dumping the system that everyone (and I
> > don't just mean people on this list -- I mean the wider open source
> > community as well) knows how to use and has worked reliably for years
> > (decades, really) to be replaced by a system that everyone is having
> > problems with (it's not just me -- others are running into trouble too
> > -- just look at this thread). It's just not ready yet.
> >
> 
> I've kinda stayed out of this discussion as I wanted to see which way
> the wind was blowing, and I like to tune my workflows to the project
> not vice-versa as much as possible.
> 
> At this point I don't like using meson in my workflows for two main
> reasons: (mostly like Ilia)
> 
> a) meson upgrades crap out my builddirs. (0.49 will fix it? then yay
> when 0.49 lands in distros, I'll consider this done)

This is supposed to be fixed in 0.49.0.

> b) I can't extract either the original configuration line or even a
> give me a command line to reproduce the current state so I can cut and
> paste it.

The fix for a) stores the information to get the configuration back (it's in an
ini file, so not great for readability). I can write a patch to print the line
in a printable form.

Dylan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20181214/5fa6ec47/attachment.sig>


More information about the mesa-dev mailing list