On Fri, Jan 16 2015, Jose Fonseca wrote: > Oh, just saying that in fact I got it to build that module on Windows.
Thanks. That's good to know. I appreciate that testing.
I've just pushed this series along with your fixes.
And for the sake of everyone that contributed to the discussion on the
SHA-1 dependency, here's where things stand currently:
With autotools:
If a supported SHA-1 library is detected, the resulting Mesa
library will be linked against it.
If no supported library is detected, Mesa will still compile,
but without any of the code that might require a SHA-1
implementation, (none today, but a shader cache is expected
in the near future).
In either case, the dependency can be avoided by running
configure with the option --disable-shader-cache.
With scons:
Regardless of the presence or absence of SHA-1 libraries, Mesa
will not be linked against any, nor will any of the SHA-1-using
code be compiled. This is effectively the same situation one
would get with --disable-shader-cache in the autotools case.
In the future, I expect the situation with scons to match that of
autotools, (so that the shader cache could be made available in scons
builds). José volunteered to write the scons magic to detect SHA-1
implementations as time permits.
Additionally, some people mentioned the possibility of adding a SHA-1
implementation directly to Mesa, (to allow for the shader-cache to be
used without any external dependency). If someone wants to pursue that,
that's still a possibility. But that's not something I plan to pursue
myself.
-Carl
pgp41DBd0mvsR.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
