Skip to content
Snippets Groups Projects
  1. Oct 26, 2020
  2. Sep 08, 2020
  3. Sep 07, 2020
  4. Aug 24, 2020
  5. Aug 20, 2020
  6. Jul 29, 2020
    • Jordan Petridіs's avatar
      amrnbenc: remove global variables · 995a135d
      Jordan Petridіs authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      gstcheck is declaring its own buffers glist which ends up
      overwritten, loks like the code meant to use that already
      
      gcc 10 is also complaining about this, but only on static
      builds for some reason
      
      ```
      FAILED: subprojects/gst-plugins-ugly/tests/check/elements_amrnbenc
      /usr/bin/ld: subprojects/gstreamer/libs/gst/check/libgstcheck-1.0.a(gstcheck.c.o):(.bss+0x38): multiple definition of `buffers'; subprojects/gst-plugins-ugly/tests/check/708af1f@@elements_amrnbenc@exe/elements_amrnbenc.c.o:(.bss+0x18): first defined here
      collect2: error: ld returned 1 exit status
      ```
      
      also remove unused var `current_buf`
      
      Part-of: <!62>
      995a135d
  7. Jul 27, 2020
  8. Jul 25, 2020
  9. Jul 24, 2020
  10. Jul 22, 2020
  11. Jul 21, 2020
  12. Jul 10, 2020
  13. Jul 08, 2020
  14. Jul 03, 2020
  15. Jul 02, 2020
  16. Jun 22, 2020
  17. Jun 19, 2020
  18. Jun 10, 2020
  19. Jun 08, 2020
  20. Jun 06, 2020
  21. Jun 05, 2020
  22. Jun 04, 2020
  23. Jun 02, 2020
  24. May 27, 2020
    • Tim-Philipp Müller's avatar
      tests: fix meson test env setup to make sure we use the right gst-plugin-scanner · 4063a319
      Tim-Philipp Müller authored
      If core is built as a subproject (e.g. as in gst-build), make sure to use
      the gst-plugin-scanner from the built subproject. Without this, gstreamer
      might accidentally use the gst-plugin-scanner from the install prefix if
      that exists, which in turn might drag in gst library versions we didn't
      mean to drag in. Those gst library versions might then be older than
      what our current build needs, and might cause our newly-built plugins
      to get blacklisted in the test registry because they rely on a symbol
      that the wrongly-pulled in gst lib doesn't have.
      
      This should fix running of unit tests in gst-build when invoking
      meson test or ninja test from outside the devenv for the case where
      there is an older or different-version gst-plugin-scanner installed
      in the install prefix.
      
      In case no gst-plugin-scanner is installed in the install prefix, this
      will fix "GStreamer-WARNING: External plugin loader failed. This most
      likely means that the plugin loader helper binary was not found or
      could not be run. You might need to set the GST_PLUGIN_SCANNER
      environment variable if your setup is unusual." warnings when running
      the unit tests.
      
      In the case where we find GStreamer core via pkg-config we use
      a newly-added pkg-config var "pluginscannerdir" to get the right
      directory. This has the benefit of working transparently for both
      installed and uninstalled pkg-config files/setups.
      
      Part-of: <gstreamer/gst-plugins-ugly!53>
      4063a319
    • Guillaume Desmottes's avatar
      dvdreadsrc: fix uninitialized warning · 887416db
      Guillaume Desmottes authored
      Variable is always set in actual code paths but let's keep gcc happy.
      
      Part-of: <gstreamer/gst-plugins-ugly!51>
      887416db
  25. May 11, 2020
  26. Apr 08, 2020
    • Derek Lesho's avatar
      asfdemux: Always re-initialize metadata and global_metadata · 8fe8ed3d
      Derek Lesho authored and Sebastian Dröge's avatar Sebastian Dröge committed
      When transitioning from the PAUSED state, to the READY state, and back,
      metadata and global_metadata are left uninitialized, unlike when the
      demxuer transitions from NULL to READY, then to PAUSED.  I have found
      this to cause a segmentation fault when fields in these structures are
      set.
      8fe8ed3d
  27. Apr 02, 2020
Loading