1. 10 Oct, 2018 8 commits
  2. 08 Oct, 2018 4 commits
  3. 04 Oct, 2018 4 commits
  4. 03 Oct, 2018 1 commit
  5. 01 Oct, 2018 2 commits
  6. 27 Sep, 2018 1 commit
  7. 26 Sep, 2018 1 commit
  8. 24 Sep, 2018 4 commits
    • Sebastian Dröge's avatar
      glmixerbin: "latency" property on aggregator is uint64, not int64 · 47b69bca
      Sebastian Dröge authored
      Also update the property description and range with aggregator's values.
      47b69bca
    • Tim-Philipp Müller's avatar
      96ac822b
    • Tim-Philipp Müller's avatar
      libs: fix API export/import and 'inconsistent linkage' on MSVC · b6411ae7
      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.
      
      While we're at it, 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
      b6411ae7
    • Tim-Philipp Müller's avatar
      docs: plugins: update for git master · be3edc6a
      Tim-Philipp Müller authored
      be3edc6a
  9. 22 Sep, 2018 2 commits
  10. 21 Sep, 2018 13 commits