1. 24 Sep, 2018 1 commit
    • Tim-Philipp Müller's avatar
      libs: figure out right export define in configure · 57c8e014
      Tim-Philipp Müller authored
      Add new GST_API_EXPORT in config.h and use that for GST_*_API
      decorators instead of GST_EXPORT.
      
      The right export define depends on the toolchain and whether
      we're using -fvisibility=hidden or not, so it's better to set it
      to the right thing directly than hard-coding a compiler whitelist
      in the public header.
      
      We put the export define into config.h instead of passing it via the
      command line to the compiler because it might contain spaces and brackets
      and in the autotools scenario we'd have to pass that through multiple
      layers of plumbing and Makefile/shell escaping and we're just not going
      to be *that* lucky.
      
      The export define is only used if we're compiling our lib, not by external
      users of the lib headers, so it's not a problem to put it into config.h
      
      Also, this means all .c files of libs need to include config.h
      to get the export marker defined, so fix up a few that didn't
      include config.h.
      
      This commit depends on a common submodule commit that makes gst-glib-gen.mak
      add an #include "config.h" to generated enum/marshal .c files for the
      autotools build.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=797185
      57c8e014
  2. 23 Sep, 2018 1 commit
    • Tim-Philipp Müller's avatar
      libs: fix 'inconsistent DLL linkage' warnings on Windows · 46ed0f04
      Tim-Philipp Müller authored
      For each lib we build export its own API in headers when we're
      building it, otherwise import the API from the headers.
      
      This fixes linker warnings on Windows when building with MSVC.
      
      The problem was that we had defined all GST_*_API decorators
      unconditionally to GST_EXPORT. This was intentional and only
      supposed to be temporary, but caused linker warnings because
      we tell the linker that we want to export all symbols even
      those from externall DLLs, and when the linker notices that
      they were in external DLLS and not present locally it warns.
      
      What we need to do when building each library is: export
      the library's own symbols and import all other symbols. To
      this end we define e.g. BUILDING_GST_FOO and then we define
      the GST_FOO_API decorator either to export or to import
      symbols depending on whether BUILDING_GST_FOO is set or not.
      That way external users of each library API automatically
      get the import.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=797185
      46ed0f04
  3. 20 Sep, 2018 1 commit
  4. 05 Sep, 2018 1 commit
  5. 31 Aug, 2018 2 commits
  6. 26 Aug, 2018 2 commits
    • Tim-Philipp Müller's avatar
      check: testclock: fix deprecation guards · 04deaac7
      Tim-Philipp Müller authored
      Make our own deprecation marker for libgstcheck,
      since the function declaration must contain the
      right API export decorator (GST_CHECK_API) and
      not the one for GStreamer core.
      04deaac7
    • Tim-Philipp Müller's avatar
      bitwriter: fix compiler warning · f7b5151b
      Tim-Philipp Müller authored
      Don't return a value from a function that doesn't
      return a value using the returned value from a
      function that also doesn't return a value.
      
      gstbitwriter.h(265): warning C4098: 'gst_bit_writer_align_bytes_unchecked': 'void' function returning a value
      f7b5151b
  7. 16 Aug, 2018 1 commit
  8. 14 Aug, 2018 2 commits
  9. 12 Aug, 2018 2 commits
  10. 11 Aug, 2018 1 commit
  11. 10 Aug, 2018 1 commit
  12. 02 Aug, 2018 1 commit
  13. 01 Aug, 2018 1 commit
  14. 27 Jul, 2018 1 commit
  15. 25 Jul, 2018 3 commits
  16. 24 Jul, 2018 2 commits
  17. 19 Jul, 2018 1 commit
  18. 16 Jul, 2018 1 commit
  19. 13 Jul, 2018 1 commit
  20. 09 Jul, 2018 1 commit
  21. 07 Jul, 2018 2 commits
  22. 24 Jun, 2018 1 commit
  23. 05 Jun, 2018 1 commit
    • Edward Hervey's avatar
      baseparse: Ensure seqnum consistency · d34f0460
      Edward Hervey authored
      We need all relevant events of a segment to have consistent seqnum:
      * GST_EVENT_SEGMENT
      * GST_EVENT_EOS
      
      If we are push-based and create a new segment, use the same seqnum
      as the upstream event.
      
      If we are pull-based, use the seqnum of that newly created segment
      event everywhere
      d34f0460
  24. 03 Jun, 2018 1 commit
  25. 30 May, 2018 1 commit
  26. 16 May, 2018 1 commit
  27. 07 May, 2018 2 commits
  28. 06 May, 2018 1 commit
  29. 05 May, 2018 2 commits
  30. 01 May, 2018 1 commit