Andreas Enge <andr...@enge.fr> writes: >> (Actually there are also some .py files in the source tree which I'm >> told might be necessary at build time regardless of rebuilding the build >> system, but this doesn't seem to be the case for us, maybe because >> they're only needed for some optional features which we don't have >> enabled.) > > There is the following comment: > ;; TODO: Add 'libxml2-python' for OpenGL ES 1.1 and 2.0 support > So maybe python might be needed one day, but is not needed now? > Did you try to check that the outcome is "the same" when dropping python? > There are no missing features that are more or less silently dropped when > removing python?
I did a diff of every file in the output before and after dropping gettext, flex, bison, and python from native-inputs, and barring for the output's own hash, files were bit-identical. (I copied the store items to somewhere, ran 'sed -i s/<hash>//' on every file (via find) for each item with its hash, then did a recursive diff.) > The mesa install page > http://mesa3d.org/install.html > states the following: > "1. Prerequisites for building > 1.1 General > Python - Python is required. Version 2.6.4 or later should work. > Python Mako module - Python Mako module is required. Version 0.7.3 or > later should work. > SCons is required for building on Windows and optional for Linux (it's an > alternative to autoconf/automake.)" I've been told that Python/mako are used when rebuilding parts of the build system, which apparently many people do because they frequently edit some grammar files (hence also bison). I pushed the patch to core-updates now. Taylan