On 17 August 2018 at 18:59, Dylan Baker <dy...@pnwbakers.com> wrote: > Quoting Emil Velikov (2018-08-17 04:11:32) >> From: Dylan Baker <dy...@pnwbakers.com> >> >> There are multiple reasons why the python scripts are executed >> explicitly via $PYTHON or equivalent. In random order: >> >> - env is rarely a thing on Windows > > windows does something completely different based on file extensions, however > IUC, the python loader for windows does actually read the shbang to decide > whether to invoke python 2 or python 3, so that might not be a problem > >> - env can be outside of /usr/bin/ > > Ah Haiku. :) > There are other exotic OS which [attempt to] use Mesa - Hurd, NixOS, Genode, etc ;-)
>> - the python executable varies across platforms - pythonX.Y, python >> - we want to use the same python version everywhere in Mesa >> - executing the scripts manually, doesn't ensure all the dependencies >> are built and up-to date > > This is not true for meson, meson runs tests all at once after all > building/re-building is complete. > I think you missed "manually" in my statement. Thanks Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
