On 16 January 2018 at 17:57, Eric Engestrom <eric.engest...@imgtec.com> wrote: > On Tuesday, 2018-01-16 10:36:49 -0500, Chuck Atkins wrote: >> When only a single SWR architecture is being used, this allows that >> architecture to be builtin rather than as a separate libswrARCH.so that >> gets loaded via dlopen. Since there are now several different code >> paths for each detected CPU architecture, the log output is also >> adjusted to convey where the backend is getting loaded from. >> >> This also allows SWR to be used for static mesa builds which are still >> important for large HPC environments where shared libraries can impose >> unacceptable application startup times as hundreds of thousands of copies >> of the libs are loaded from a shared parallel filesystem. >> >> Based on an initial implementation by Tim Rowley. >> >> Signed-off-by: Chuck Atkins <chuck.atk...@kitware.com> >> CC: Tim Rowley <timothy.o.row...@intel.com> >> CC: Bruce Cherniak <bruce.chern...@intel.com> >> --- >> configure.ac | 12 ++++- >> src/gallium/drivers/swr/Makefile.am | 48 +++++++++++++---- > > Meson needs these changes as well. > Don't forget SCons ;-)
Perhaps one can split out the .cpp and build changes somehow. Thus interested parties can update the build system of their preference as they have time? -Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
