1. 07 Jul, 2015 1 commit
  2. 08 Jun, 2015 1 commit
    • Luca Barbato's avatar
      configure: Support MSVC 2015 · a6f19d6a
      Luca Barbato authored
      The C runtime C99 compatibility had been improved a lot and it now
      rejects some of the compatibility defines provided for the older
      versions.
      
      Many thanks to Ray for the time spent testing.
      
      Bug-Id: 864
      CC: libav-stable@libav.org
      a6f19d6a
  3. 06 May, 2015 1 commit
  4. 06 Mar, 2015 1 commit
  5. 10 Feb, 2015 1 commit
  6. 05 Jan, 2015 1 commit
  7. 24 Nov, 2014 1 commit
  8. 15 Aug, 2014 1 commit
  9. 04 Aug, 2014 1 commit
  10. 25 Apr, 2014 1 commit
  11. 24 Apr, 2014 2 commits
  12. 22 Apr, 2014 1 commit
  13. 26 Jan, 2014 1 commit
  14. 25 Jan, 2014 1 commit
  15. 09 Dec, 2013 1 commit
  16. 21 Oct, 2013 1 commit
  17. 17 Oct, 2013 1 commit
    • Stefano Sabatini's avatar
      lavu/channel_layout: change av_get_channel_layout() behavior at the next bump · d96e377c
      Stefano Sabatini authored
      The new syntax is preferred since it allows backward syntax compatibility
      with libswr when switching to the new option handling code with
      AV_OPT_TYPE_CHANNEL_LAYOUT.
      
      With the new parser the string:
      1234
      
      is interpreted as a channel layout mask, rather than as a number of
      channels, and thus it's compatible with the current way to set a channel
      layout as an integer (e.g. for the icl and ocl options) making use of
      integer option values.
      
      ff_get_channel_layout() with compat=0 will be used in the
      AV_OPT_TYPE_CHANNEL handler code.
      
      The user is encouraged to switch to the new forward compatible syntax,
      which requires to put a trailing "c" when specifying a layout as a number
      of channels.
      d96e377c
  18. 20 Sep, 2013 1 commit
    • Alex Smith's avatar
      msvc/icl: Use __declspec(deprecated) · 09f2581d
      Alex Smith authored
      Prior to this on msvc/icl there was no handling of deprecated functions
      and the deprecated warning was disabled.
      
      After enabling there are a number of warnings relating to the CRT and
      the use of the non-secure versions of several functions.  Defining
      _CRT_SECURE_NO_WARNINGS silences these warnings.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      09f2581d
  19. 10 Aug, 2013 1 commit
  20. 09 Aug, 2013 2 commits
    • Martin Storsjö's avatar
      libavutil: Make avpriv_open a library-internal function on msvcrt · e743e7ae
      Martin Storsjö authored
      Add one copy of the function into each of the libraries, similarly
      to what we do for log2_tab. When using static libs, only one
      copy of the file_open.o object file gets included, while when
      using shared libraries, each of them get a copy of its own.
      
      This fixes DLL builds with a statically linked C runtime, where
      each DLL effectively has got its own instance of the C runtime,
      where file descriptors can't be shared across runtimes.
      
      On systems not using msvcrt, the function is not duplicated.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      e743e7ae
    • Martin Storsjö's avatar
      libavutil: Enable the MSVC DLL symbol loading workaround in shared builds as well · 33237123
      Martin Storsjö authored
      This used to only be necessary in static builds (when using the
      dynamically linked C runtime), since the _imp prefixed symbols do
      exist when linking to the actual DLL. When building testprogs,
      however, the current library (e.g. libavutil for some of the testprogs)
      is linked statically.
      
      This fixes make fate on DLL builds when using the dynamically
      linked C runtime.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      33237123
  21. 07 Aug, 2013 1 commit
  22. 02 Aug, 2013 1 commit
  23. 13 May, 2013 1 commit
  24. 07 May, 2013 1 commit
  25. 13 Mar, 2013 1 commit
  26. 14 Feb, 2013 2 commits
  27. 12 Feb, 2013 1 commit
  28. 09 Feb, 2013 1 commit
  29. 08 Feb, 2013 1 commit
  30. 18 Jan, 2013 1 commit
  31. 26 Nov, 2012 1 commit
  32. 25 Nov, 2012 1 commit
    • Janne Grunau's avatar
      remove #defines to prevent use of discouraged external functions · e96d90ee
      Janne Grunau authored
      Preventing the use of discouraged or 'insecure' external functions
      through defines in an internal header is not a good solution. The
      header is not guaranteed to be included universally which makes
      overlooking bad use of said functions during review more likely.
      
      There are cases were those functions either are the most straight
      forward solution or even have to be used. Using malloc or free is
      required if the allocation or release is done by other libraries.
      e96d90ee
  33. 18 Oct, 2012 1 commit
    • Martin Storsjö's avatar
      Add support for building shared libraries with MSVC · d66c52c2
      Martin Storsjö authored
      This requires the makedef perl script by Derek, from the
      c89-to-c99 repo. That scripts produces a .def file, listing
      the symbols to be exported, based on the gcc version scripts
      and the built object files.
      
      To properly load non-function symbols from DLL files, the
      data symbol declarations need to have the attribute
      __declspec(dllimport) when building the calling code. (On mingw,
      the linker can fix this up automatically, which is why it has not
      been an issue so far. If this attribute is omitted, linking
      actually succeeds, but reads from the table will not produce the
      desired results at runtime.)
      
      MSVC seems to manage to link DLLs (and run properly) even if
      this attribute is present while building the library itself
      (which normally isn't recommended) - other object files in the
      same library manage to link to the symbol (with a small warning
      at link time, like "warning LNK4049: locally defined symbol
      _avpriv_mpa_bitrate_tab imported" - it doesn't seem to be possible
      to squelch this warning), and the definition of the tables
      themselves produce a warning that can be squelched ("warning C4273:
      'avpriv_mpa_bitrate_tab' : inconsistent dll linkage, see previous
      definition of 'avpriv_mpa_bitrate_tab').
      
      In this setup, mingw isn't able to link object files that refer to
      data symbols with __declspec(dllimport) without those symbols
      actually being linked via a DLL (linking avcodec.dll ends up with
      errors like "undefined reference to `__imp__avpriv_mpa_freq_tab'").
      The dllimport declspec isn't needed at all in mingw, so we simply
      choose not to declare it for other compilers than MSVC that requires
      it. (If ICL support later requires it, the condition can be extended
      later to include both of them.)
      
      This also implies that code that is built to link to a certain
      library as a DLL can't link to the same library as a static library.
      Therefore, we only allow building either static or shared but not
      both at the same time. (That is, static libraries as such can be,
      and actually are, built - this is used for linking the test tools to
      internal symbols in the libraries - but e.g. libavformat built to
      link to libavcodec as a DLL cannot link statically to libavcodec.)
      
      Also, linking to DLLs is slightly different from linking to shared
      libraries on other platforms. DLLs use a thing called import
      libraries, which is basically a stub library allowing the linker
      to know which symbols exist in the DLL and what name the DLL will
      have at runtime.
      
      In mingw/gcc, the import library is usually named libfoo.dll.a,
      which goes next to a static library named libfoo.a. This allows
      gcc to pick the dynamic one, if available, from the normal -lfoo
      switches, just as it does for libfoo.a vs libfoo.so on Unix. On
      MSVC however, you need to literally specify the name of the import
      library instead of the static library.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      d66c52c2
  34. 03 Oct, 2012 1 commit
  35. 30 Aug, 2012 1 commit
  36. 10 Aug, 2012 1 commit
  37. 09 Aug, 2012 1 commit