-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GstGL GLMixer processTextures function is generated as invalid function #175
Comments
Thanks for the issue reports! This one is a bug in GStreamer. You can work around it by editing the gir file: simply remove the I can't fix this in java-gi, unless I start second-guessing the |
Thanks for addressing these issues so quickly! If this is a problem in the gir file and you have to patch similar issues even in the GObject and Gio gir files, should this be an issue opened upstream? I couldn't find a related issue in gobject-introspection or a reference to similar issues in other bindings. The rust bindings don't seem to parse the Additionally or alternatively, checking whether the parameters match in |
Agreed, checking if the parameters match is a reasonable check. I’ll try it out. |
The issue with GLMixer is now resolved, when the bindings are generated with the newest java-gi from the main branch. |
This seems to be a corner-case in code generation.
The virtual-method and method signatures for
processTextures
inGLMixer
don't match. One expects aGstGLMemory out_tex
, and the other expectsGstBuffer out_buf
. This results in generated code usingoutTex
without declaring it.Despite having the same name,
processTextures(Buffer outbuf)
and the virtual methodprocessTextures(GLMemory outtex)
aren't the same method. The one taking theBuffer
should callgst_gl_mixer_process_textures
, while the one taking theGLMemory
is called withingst_gl_mixer_process_textures
and is implemented/overriden by subclasses.Looking through gstreamer git, this was introduced 12 years ago: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/89569276c563d3343417ea5e34bddcd0714131d7
The text was updated successfully, but these errors were encountered: