• Advertisement
Sign in to follow this  

OpenGL OpenGL extension initialization

This topic is 3189 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi there. I'm trying to keep my GL framework simple, and i'm currently facing a design doubt. How to initialize the extensions? Like, the framework is made up of several cpp files, so when i try to declare the extensions in an .h file, it just gives me linker errors, saying that those functions are already declared on the previous cpp file. All those files should have access to the extensions. For example, I have a couple of files for shaders, one file for general opengl operations, among other things. the shader files should have access to the function pointers, just as the general opengl file. How to do this? I tried using "external " keyword on the declaration, and then redeclaring them on the main cpp, and initialize them there. I'd assume all the cpp files would have access to the now initialized func pointers. Didn't work. Also tried creating a singleton class, only for extension pointers, with static members. Compiler borked on me. This is g++/linux. Any ideas?

Share this post


Link to post
Share on other sites
Advertisement
Why don't you just use GLee or GLEW?

Otherwise, check for the GL_VERSION_[mayor]_[minor] macro before declaring your functions, for example:


#ifndef GL_VERSION_2_0
// define GL 2.0 extensions here
#endif


Share this post


Link to post
Share on other sites
Quote:
Original post by Rhiakath
Hi there. I'm trying to keep my GL framework simple, and i'm currently facing a design doubt. How to initialize the extensions? Like, the framework is made up of several cpp files, so when i try to declare the extensions in an .h file, it just gives me linker errors, saying that those functions are already declared on the previous cpp file. All those files should have access to the extensions. For example, I have a couple of files for shaders, one file for general opengl operations, among other things. the shader files should have access to the function pointers, just as the general opengl file. How to do this? I tried using "external " keyword on the declaration, and then redeclaring them on the main cpp, and initialize them there. I'd assume all the cpp files would have access to the now initialized func pointers.


Yes, it will work. Declare as extern in a single .h file. include that .h in all your .cpp files. Keep the definition in a single .cpp file.
That's what I use to do. Then I moved to glew.

Share this post


Link to post
Share on other sites
Yes, I was using glew too, but i wanted to do the initialization myself, because i don't understand some minor stuff about glew.
Also, if I have the glCreateShaderARB extension, and also the glCreateShader core function, should I use the core, or the extension? Why are the pointers different? Since it's now part of core, shouldn't the pointers to the functions point to the same place?

Share this post


Link to post
Share on other sites
Quote:
Original post by Rhiakath
Yes, I was using glew too, but i wanted to do the initialization myself, because i don't understand some minor stuff about glew.
Also, if I have the glCreateShaderARB extension, and also the glCreateShader core function, should I use the core, or the extension? Why are the pointers different? Since it's now part of core, shouldn't the pointers to the functions point to the same place?


Because one returns a GLhandleARB, and the core version uses GLuint's as handles.

I prefer core versions, but is just me :)

Share this post


Link to post
Share on other sites
rhiakath@Gentoo /usr/include/GL $ grep GLhandleARB *

glext.h:typedef unsigned int GLhandleARB; /* shader object handle */


So, they're both the same. So, the only difference is really the function pointer. Supposedly they both do the same. Do you guys know any reason for the pointer not be the same?

Also, the reason because I wanted to do my own initializing was just because I was planning to do something like, if both funcs are available, then both pointers point to the core func. That way, I would always use the call to the core func, and let the pointers do the rest durint init.
I would not have to have a gazillion if's spread across the code to see if the function is available as core, instead of extension.

Share this post


Link to post
Share on other sites
If you really want to do your own initialisation (I'm doing that because I find Glee's mere code size and parse overhead unacceptable), you're probably off best writing a spec parser and automatising the process.
You can grab all the extensions in 3-4 minutes off opengl.org with wget. When a new extension that you want to use 4comes out, download that additional spec and re-run your tool for a new header/source pair.

What you need for the extension loading are the names of functions. You don't have to care about constants or everything else, all that is already in glext.h.
In every spec file, you find the names of the functions in the section labelled New\s+(Functions|Procedures)+ (it may be "functions and procedures" or "procedures and functions", sometimes it's "functions, procedures, and something else" too).
The typedefs for the function pointers in glext.h are named PFNGL(NAME-OF-FUNCTION)PROC, which is easy enough to automate.
You'll want to declare extern global variables for the function pointers and have a source file that defines each of them and that has a "init" function of some sort which retrieves the addresses. From your point of view, they'll work like plain ordinary functions later.

I'm doing the spec parsing using a PHP script, as PHP nicely supports reading files into an array, running a regex over them, and building the output header/source, eleminating duplicate elements etc. You'd probably take half a year coding that in C whereas it's a mere afternoon and under 500 lines of code (including formatting) in PHP. Other people may prefer perl instead (which I'm uncomfortable with), it sure does the job just fine, too -- use what you like.

Two things to watch for:
1. Some functions may be defined identically in two (or possibly more) extension specs, so you must make sure you don't break the one-definition-rule. PHP's array_unique() is your friend here.
2. glext.h may be erroneous. This is currently (revision of march 27, 2009) the case with ARB_instanced_arrays, which lacks the ARB suffix in its function pointer names. Unluckily, there is no easy way to deal with this in an automated manner.
GLee implements this extension wrong (in accordance with glext.h) which of course works fine. You might do the same or you could edit glext.h, or you could wait and hope that they fix it eventually (and you might not need that particular extension at all).

Share this post


Link to post
Share on other sites
Quote:
Original post by Rhiakath
rhiakath@Gentoo /usr/include/GL $ grep GLhandleARB *

glext.h:typedef unsigned int GLhandleARB; /* shader object handle */


So, they're both the same.

Purely an implementation detail. As far as OpenGL and the interface is concerned, the types are different; one is GLuint and one is GLhandleARB.

Quote:
Original post by Rhiakath
So, the only difference is really the function pointer. Supposedly they both do the same. Do you guys know any reason for the pointer not be the same?

Supposedly they both do the same? If you cannot guarantee that they are, in fact, doing exactly the same thing, then...

Quote:
Original post by Rhiakath
Also, the reason because I wanted to do my own initializing was just because I was planning to do something like, if both funcs are available, then both pointers point to the core func. That way, I would always use the call to the core func, and let the pointers do the rest durint init.
I would not have to have a gazillion if's spread across the code to see if the function is available as core, instead of extension.

... really is a bad idea. Given that you say the function pointers returned are different suggest that you should be very careful.

Even though the documentation suggests they behave the same, there could be subtle differences as allocating names from different pools, accepting slightly different parameters (maybe the ARB-variant accept some additional parameter for some other extension, like geometry shaders which is not a part of the core), or otherwise behaving different internally. Subtle differences like that may not be obvious from the documentation. The API and interface makes a difference between the function (the name), the driver exposes different entry points, so you better treat them as different.

Share this post


Link to post
Share on other sites
I use GLEW in my engine, found it extremely easy to install and use and grants me instant access to the extensions I need. However, even if it says that a core function is supported as core, I still use the ARB one, simply because 1) it's easy than programming two different ways for different users based on whether it's supported or not 2) I had issues with FBO's not working when using the Core functions exposed through GLEW.

Share this post


Link to post
Share on other sites
I assumed they do the same thing, not that they do it the same way.
And, of course, I'd only do this with functions that had similar signatures, right?

Now, is it really needed for me to have a thousand if's, just checking if the core function is available, and if not use the extension?
Is there no other way?

Share this post


Link to post
Share on other sites
Ok, maybe you guys can help me out if I show you a little snippet.

Tihs is a part of the main() function.

int main ( int argc, char *argv[] )
{
OpenGL::CGLContext Context;

Context.Initialize();
Context.CreateWindow();
.
.
.
OpenGL::CGLShaderProgram Program;
OpenGL::CGLShader VS, PS;
glCreateShader(GL_VERTEX_SHADER);
Context.InitializeExtensions();
glCreateShader(GL_VERTEX_SHADER);
VS.LoadFromFile ( OpenGL::CGLShader::VERTEX_SHADER, "default.vertex_shader" );

So, inside Initialize, all it does is create a context, then create a window to that context. Get extensions, destroy window (not the context).

The problem is, glCreateShader resolves just fine, when i get the pointer. the debugger shows me an address, and successfully resolves it into the func name, so I check it's correct.
after it leaves Initialize(), it comes to glCreateShader.
It segfaults here.
If I comment out that line, it just segfaults on the next glCreateShader, even after getting the func pointers again inside InitializeExtensions.
The only way it does not segfault, is if I call glCreateShader inside InitializeExtensions.

Nevertheless, the pointer remains with the same value all across the whole session.

What's happening here?

Share this post


Link to post
Share on other sites
OpenGL::CGLShaderProgram Program;
OpenGL::CGLShader VS, PS;
glCreateShader(GL_VERTEX_SHADER);
Context.InitializeExtensions();

If I am reading this right you have glCreateShader() called before you initialize the extensions?

Share this post


Link to post
Share on other sites
Quote:
Original post by Rhiakath
And, of course, I'd only do this with functions that had similar signatures, right?

I assume you mean identical signature, not similar. Similar signature implies there is a difference in the signature, and then they definitely are different. But still, identical signature does in no way imply same functionality.

Quote:
Original post by Rhiakath
Now, is it really needed for me to have a thousand if's, just checking if the core function is available, and if not use the extension?
Is there no other way?

No, it is not needed to make thousands of ifs to get around this. A few perhaps if you wrap it. For example, wrap shader functions around some unified interface, and then let the implementation of the interface deal with different extension and core support.

GLuint loadprogram(GLuint vshader, GLuint fshader)
{
GLuint program = glCreateProgram();
glAttachShader(program, vshader);
glAttachShader(program, fshader);
glLinkProgram(program);
return program;
}

A quick example using the core variants to create a program with a vertex and a fragment shader. A single if is needed to make this use the ARB-variants when needed and I can still load all my shaders from thousands of places, which would need thousands of ifs without the wrapper.

Share this post


Link to post
Share on other sites
Reading only that part, it would seem so. But as I said, it is calling Initialize Extensions inside Initialize, right at the beginning.
I'm just trying to figure out where it breaks, so I'm calling it twice, and enveloping it with glCreateShader.

Share this post


Link to post
Share on other sites
Some more replies there before my post. Looks like there are some wrapper classes for shaders there, which is what I'm talking about. Don't use OpenGL-code directly everywhere; wrap it and use the interface instead.

Share this post


Link to post
Share on other sites
That is what I'm doing. unfortunately, the opengl calls inside the shader class all segfault. I just added the opengl calls here to be able to see where it screws up. What bothers me, is that between the initialize call, and the shader loading call, there is nothing. and the pointer remains the same. why does it segfault?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By reenigne
      For those that don't know me. I am the individual who's two videos are listed here under setup for https://wiki.libsdl.org/Tutorials
      I also run grhmedia.com where I host the projects and code for the tutorials I have online.
      Recently, I received a notice from youtube they will be implementing their new policy in protecting video content as of which I won't be monetized till I meat there required number of viewers and views each month.

      Frankly, I'm pretty sick of youtube. I put up a video and someone else learns from it and puts up another video and because of the way youtube does their placement they end up with more views.
      Even guys that clearly post false information such as one individual who said GLEW 2.0 was broken because he didn't know how to compile it. He in short didn't know how to modify the script he used because he didn't understand make files and how the requirements of the compiler and library changes needed some different flags.

      At the end of the month when they implement this I will take down the content and host on my own server purely and it will be a paid system and or patreon. 

      I get my videos may be a bit dry, I generally figure people are there to learn how to do something and I rather not waste their time. 
      I used to also help people for free even those coming from the other videos. That won't be the case any more. I used to just take anyone emails and work with them my email is posted on the site.

      I don't expect to get the required number of subscribers in that time or increased views. Even if I did well it wouldn't take care of each reoccurring month.
      I figure this is simpler and I don't plan on putting some sort of exorbitant fee for a monthly subscription or the like.
      I was thinking on the lines of a few dollars 1,2, and 3 and the larger subscription gets you assistance with the content in the tutorials if needed that month.
      Maybe another fee if it is related but not directly in the content. 
      The fees would serve to cut down on the number of people who ask for help and maybe encourage some of the people to actually pay attention to what is said rather than do their own thing. That actually turns out to be 90% of the issues. I spent 6 hours helping one individual last week I must have asked him 20 times did you do exactly like I said in the video even pointed directly to the section. When he finally sent me a copy of the what he entered I knew then and there he had not. I circled it and I pointed out that wasn't what I said to do in the video. I didn't tell him what was wrong and how I knew that way he would go back and actually follow what it said to do. He then reported it worked. Yea, no kidding following directions works. But hey isn't alone and well its part of the learning process.

      So the point of this isn't to be a gripe session. I'm just looking for a bit of feed back. Do you think the fees are unreasonable?
      Should I keep the youtube channel and do just the fees with patreon or do you think locking the content to my site and require a subscription is an idea.

      I'm just looking at the fact it is unrealistic to think youtube/google will actually get stuff right or that youtube viewers will actually bother to start looking for more accurate videos. 
    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
  • Advertisement