@landelare @aeva I was using printf in a CPU side program, to print the "GLEW_ARB_shader_image_load_store" variable, which I think the OpenGL Extension Wrangler would set to 1, if ARB_shader_image_load_store was supported by my graphics card.
I made sure to call glewInit and have a valid context and all.
@landelare as of version 1.1.0, GLEW signals extension availability with variables containing boolean values, so while the examples KT is posting look like name constants, they're mutable binary values that the initialization code sets up. relevant docs: https://glew.sourceforge.net/basic.html
@kertinker what GL version are you targeting and what platform? for a sanity check, could you post what GLEW_ARB_vertex_program is after init?
@aeva @landelare Oh, sure. I don't have a "glxinfo" command, but visualinfo produces this: https://nopaste.net/l92XzrU5kr which... oddly includes GL_EXT_shader_image_load_store.
I'm clearly doing something wrong. Not sure how I could get a working OpenGL program running, without it saying extensions that are supported, are supported. Maybe you have to set a specific... mode, before they get supported?
@aeva @landelare https://nopaste.net/aTFTXWDVRU
Other than that just the usual gtk init and creating a GtkGlArea.
@kertinker @landelare I'm not familiar with GtkGlArea, but I spotted this in the docs https://docs.gtk.org/gtk4/method.GLArea.set_required_version.html
You have to call gtk_gl_area_set_required_version before the widget's rendering context is created, but I imagine if you set it to 4.6 (based on your earlier visualinfo paste) then you should be able to see the extensions you are missing. Ideally you'll want to set it to the lowest required version you need, but 4.6 is fine for debugging.
@aeva Huh, it must default to a really low version, which is why so many extensions say they're unsupported. Thanks so much! I'll go try it right away.
...
Yes, all extensions except ARB_vertex_program are now supported!