On 12/4/06, <b class="gmail_sendername">Hans-Christoph Steiner</b> &lt;<a href="mailto:hans@eds.org">hans@eds.org</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><br>Ok, wait I think I misunderstood.&nbsp;&nbsp;You are saying that the ancient<br>ATI card in the autobuild machines might support the nvidia<br>extensions, and they are being properly detected.&nbsp;&nbsp;I thought you mean<br>whether the card was nvidia or not (neither are).
</blockquote><div><br>There are extensions to OpenGL which are vendor specific and some vendors may support ones that are not their own.&nbsp; In this case glDeleteProgramsNV has to do with vertex and fragment shaders and Nvidia had their own extension before it was approved by the review board for full GL status.&nbsp; I think that glDeleteProgramsNV could be removed since glDeleteProgramsARB covers the same functionality.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It seems to load from the command line with -nogui, I am testing now<br>whether I can load an object.
</blockquote><div><br>The ATI drivers should not define the NV extension in the headers if it is not supported by the driver.&nbsp; All GEM does is have an #ifdef for the presence of that extension and then builds with it enabled or not.
<br><br>So, does the autobuild GEM run on the autobuild machine?<br></div><br></div><br>