On Wed, Feb 26, 2020 at 12:16 PM Jose Fonseca <jfons...@vmware.com> wrote: > > > but it bothers me how we keep not making a decision on this. If we'd said, > > "let's keep it and support it", that would something. > > I'm surprised there's any doubt. > > SCons works great for us. Meson gives no immediate benefit for us other > than headaches. If we cared about nothing but ourselves, we'd keep SCons > indefinitely, until it became a pain. > > The only reason we don't stubbornly put the foot down is that we understand > that having one single build system would be beneficial the whole community, > and of course we appreciate all the work Dylan and others did to get Meson to > work on Windows, so we'd like to get there one day. > > That said, I don't understand why the rest of the Mesa community putting a > gun against our head to abandon SCons. > > Aren't we maintaining the SCons build? Since when in Mesa community are some > entitled to start remove code that still works, is used, and maintained by > others!!!!???? >
currently scons build is in CI, so for anyone making build system changes that effects code that is part of the scons build, they have to go and read enough stack-overflow to figure out how to make the same changes in scons ;-) BR, -R _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
