Hello Emil, On Mon, May 23, 2016 at 11:20 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote: > It seems like this won't work if one builds --enable-clover --disable-dri.
Argh, I hadn't considered this possibility. > The following should keep mesa and gallium code separate, can we try that one > ? > - move the git_sha1.h rule 'higher up' (src/Makefile.am perhaps ?) That makes perfect sense. > Please try and do the same for scons/android. I'll try. I've never used scons before thought so I might need some guidance along the way. (Doubly so considering that trying to run % scons on my work dir results in a backtrace about tuple not being callable on line 143 of the top-level SConstruct — python2 vs python3 issue maybe? This is on Debian unstable.) > - I'm split if we should have a single file or multiple or mesa and > gallium 'flavours' in respective folders. > - introduce a st/clover header (please add it in the sources lists in > Makefile.sources) which is included in the respective places. > - wire up the LLVM version/string in src/mesa (using HAVE_LLVM & > MESA_LLVM_VERSION_PATCH) > - ^^ for st/clover. > - print the LLVM version for r300 (based on r600_common_screen_init) > > How does this sound ? Well, that sort-of defeats the whole point of unifying the version string declaration, but it does make sense if we want to be selective about inclusion of the LLVM version string (to the drivers that actually use it). -- Giuseppe "Oblomov" Bilotta _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
