I don't run meson. I have a script that runs meson. I want to just run the script and I want to it configure or reconfigure.
I don't want to add this failure path into my script: "meson ... || meson --reconfigure ..." Marek On Mon, Nov 26, 2018 at 6:36 PM Dylan Baker <dy...@pnwbakers.com> wrote: > You mean you want to change the driver list? > > meson builddir > meson configure builddir -Ddri-drivers= -Dvulkan-drivers= > -Dgallium-drivers=radeonsi > ninja -C builddir # which will trigger a reconfigure > > Or was there something else you are trying to do? > > Dylan > > Quoting Marek Olšák (2018-11-26 15:29:40) > > meson has a design defect that annoys me. I have a configure script. If > I want > > to change enabled drivers and run meson, it won't configure because the > > directory exists, even if the meson parameters are different. I have to > add > > --reconfigure manually into the script. If I keep --reconfigure in the > script > > and the build directory doesn't exist, it doesn't configure. > > > > There has to be a better solution than "meson ... || meson --reconfigure > ...". > > > > Marek > > > > On Mon, Sep 17, 2018 at 12:46 PM Dylan Baker <dy...@pnwbakers.com> > wrote: > > > > 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 > > _______________________________________________ > > 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
