On Nov 10, 2016 1:34 AM, "Tapani Pälli" <<a href="mailto:tapani.palli@intel.com">tapani.palli@intel.com</a>> wrote: > > Hi; > > Here are some patches that prepare current build for Vulkan support. Hey, thanks for doing this! Reviewed-by: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>> > These are the things I noticed needing change to be able to build > upcoming <a href="http://libmesa_vulkan.intel.so">libmesa_vulkan.intel.so</a>. I'm still wondering a bit what todo > with sha1 support, there is sha1 for bionic from netbsd > (bionic/libc/upstream-netbsd/ ...) and then 9 different projects in > external/ with sha1.c included. Ideas what to do there? We already have support in Mesa for about a half a dozen different sha1 implementations. If one of those happens to already live in external/, just using that is probably easiest. Otherwise, just pick one and add it. I don't think I have much of a preference. Thanks! --Jason Ekstrand > Thanks; > > Tapani Pälli (4): > util: use STATIC_ASSERT instead of static_assert > anv: use STATIC_ASSERT instead of static_assert > android: add SPIRV_FILES to libmesa_nir > android/i965: add libmesa_i965_compiler static library > > src/compiler/<a href="http://Android.nir.mk">Android.nir.mk</a> | 3 ++- > src/intel/vulkan/anv_private.h | 4 ++-- > src/mesa/drivers/dri/i965/Android.mk | 32 ++++++++++++++++++++++++++++---- > src/util/u_vector.h | 2 +- > 4 files changed, 33 insertions(+), 8 deletions(-) > > -- > 2.7.4 > > _______________________________________________ > mesa-dev mailing list > <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a> > <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a>