No one stopped them from being in charge. They just don't write that much code as the Intel folks do.
Announcement
Collapse
No announcement yet.
Intel's GLSL2 Branch Is Merged To Mesa Master
Collapse
X
-
Originally posted by zoomblab View PostI wonder how a company with super crap OpenGL hardware (Intel) is allowed to drive important changes to Mesa? Shouldn't Nvidia/ATI be in charge of such things?
Comment
-
Originally posted by Beiruty View PostWhat does Intel Benefit from its Army of Open Source OpenGL Devs?
On the other hand, I'm pretty happy, that someone of them contributes to the vast scope of GFX.
Comment
-
Originally posted by Beiruty View PostWhat does Intel Benefit from its Army of Open Source OpenGL Devs?
It avoids reinventing the wheel pretty much.
And Intel isn't in the workstation graphics market like AMD and Nvidia, so they only need a simple driver, and don't need professional level support.
Comment
-
Well, I can't seem to be able to compile Mesa-git anymore on my Slackware-current, as the GLSL2 merge has added a hard dependency on talloc, a library distributed within Samba, at least on Slack.
The configure script does not seem to be able to find the library, while it is located in standard /use/lib64 path, and the headers are in /use/include. The version is 0.2, so it should not be very old.
configure does not give a clue on why it chokes on this one.
If anyone has an idea, I'll be gratefull.
Comment
-
Configure by default uses pkg-config to locate talloc. If your pkg-config regarding talloc is botched, you need to define TALLOC_CFLAGS and TALLOC_LIBS yourself. (note that usually if those aren't defined, pkg-config is used; hence even if you do have the headers and libs, check will fail)
Comment
Comment