Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 4 of 4

Thread: GLEW 'bug' in glslang extensions

  1. #1
    Member Regular Contributor
    Join Date
    Mar 2003
    Location
    Spain
    Posts
    273

    GLEW 'bug' in glslang extensions

    This only affects to cards that having fragment/vertex_shader extensions, haven't fragment/vertex_program.
    GLEW open this funcion pointers (glVertexAttribPointerARB, glEnableVertexAttribArrayARB and glBindAttribLocationARB) in the vp/fp_program extensions, so if your card havent these extensions (as 3DLabs WildCat VP cards), you will get an error for null function pointer if you try to use it.
    "!I don't know... fly casual"

  2. #2
    Intern Contributor
    Join Date
    Mar 2004
    Posts
    52

    Re: GLEW 'bug' in glslang extensions

    I am not exactly sure what you are saying here? Do you have a code sample or something that shows this?

  3. #3
    Junior Member Newbie
    Join Date
    Jan 2004
    Posts
    10

    Re: GLEW 'bug' in glslang extensions

    I think he is saying that the entrypoints that are shared between the extensions ARB_vertex_shader and ARB_vertex_program (e.g. glVertexAttrib4f) are not supplied by glew if ARB_vertex_program is not present but ARB_vertex_shader is.
    Essentially, both extensions describe the same entrypoints, but glew gets them from ARB_vertex_program only.

  4. #4
    Member Regular Contributor
    Join Date
    Mar 2003
    Location
    Spain
    Posts
    273

    Re: GLEW 'bug' in glslang extensions

    Yes, this is what happens exactly. This entry points are only in GL_ARB_vertex_program, but aren't in GL_ARB_vertex_shader.

    Sorry for my bad english please
    "!I don't know... fly casual"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •