On 03/28/2017 11:19 AM, Dylan Baker wrote:
Quoting Jose Fonseca (2017-03-28 09:19:48)
On 28/03/17 00:12, Dylan Baker wrote:
Okay, I have libepoxy working for windows. I also got libepoxy working as a
subproject, but it took a bit of hacking on their build system (there's
some things they're doing that make them non-subproject safe, I'll send patches
and work that out with them.
https://github.com/dcbaker/libepoxy.git fix-suproject
Thanks.
GLEW is not the only one case though. There's also FREEGLUT. So we
can't really avoid the problem of external windows binaries/subprojects.
So I've been thinking, and I suspect is better if first get things
working with binary GLEW / FREGLUT projects, then try the glew ->
libepoxy in a 2nd step, so there's less to take in to merge meson into
master.
Is freeglut a hard requirement? At least in autoconf we have logic to look for
both, and use #defines to enable freeglut only features.
Nearly all the Mesa demos require GLUT / freeglut.
-Brian
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
