1. 07 3月, 2015 1 次提交
  2. 06 3月, 2015 1 次提交
    • J
      configure, mips: remove MIPS32R2, merging it with MIPSFPU · eae13eae
      James Cowgill 提交于
      There are no independant uses of mips32r2 instructions except for the
      FPU parts. Due to the heavy use of mips32r2 specifc fpu extensions, I
      am guessing the original author intended MIPSFPU to imply MIPS32R2 anyway.
      
      Since these fpu instructions are available on mips64 (non-r2), enable them
      there as well.
      
      Also remove the last occurence of HAVE_MIPS32R2 (which is coupled to
      HAVE_MIPSFPU anyway).
      
      mips32r2 is left in the list of options form compatability so that using
      --disable-mips32r2 doesn't break anything.
      Signed-off-by: NJames Cowgill <james410@cowgill.org.uk>
      Signed-off-by: NMichael Niedermayer <michaelni@gmx.at>
      eae13eae
  3. 05 3月, 2015 1 次提交
  4. 02 3月, 2015 1 次提交
  5. 01 3月, 2015 2 次提交
  6. 26 2月, 2015 1 次提交
  7. 23 2月, 2015 2 次提交
  8. 20 2月, 2015 1 次提交
  9. 19 2月, 2015 1 次提交
  10. 17 2月, 2015 1 次提交
  11. 16 2月, 2015 1 次提交
  12. 11 2月, 2015 1 次提交
  13. 10 2月, 2015 1 次提交
  14. 08 2月, 2015 1 次提交
  15. 04 2月, 2015 1 次提交
  16. 02 2月, 2015 2 次提交
  17. 31 1月, 2015 2 次提交
  18. 27 1月, 2015 5 次提交
  19. 26 1月, 2015 1 次提交
  20. 23 1月, 2015 1 次提交
  21. 13 1月, 2015 1 次提交
  22. 10 1月, 2015 2 次提交
  23. 09 1月, 2015 1 次提交
  24. 08 1月, 2015 1 次提交
  25. 07 1月, 2015 1 次提交
    • M
      libavcodec: Add an OpenH264 encoder wrapper · 8a3d9ca6
      Martin Storsjö 提交于
      Compared to existing, common opensource H264 encoders, this can be
      useful since it has got a different license (BSD instead of GPL).
      
      Performance- and qualitywise it is comparable to x264 in ultrafast
      mode.
      
      Hooking it up as an encoder in libavcodec also simplifies comparing
      it against other common encoders.
      
      This requires OpenH264 1.3 or newer. Since the OpenH264 API and ABI
      changes frequently, only releases are supported.
      
      To take advantage of the OpenH264 patent offer, the OpenH264 library
      must not be redistributed, but downloaded at runtime at the end-user's
      system.
      Signed-off-by: NMartin Storsjö <martin@martin.st>
      8a3d9ca6
  26. 05 1月, 2015 2 次提交
  27. 03 1月, 2015 2 次提交
  28. 24 12月, 2014 1 次提交
  29. 20 12月, 2014 1 次提交
    • M
      libavformat: Only use MoveFileExA when targeting the desktop API subset · 8ebf02f8
      Martin Storsjö 提交于
      The MoveFileExA is available in the headers regardless which API
      subset is targeted, but it is missing in the Windows Phone link
      libraries. When targeting Windows Store apps, the function is
      available both in the headers and in the link libraries, and thus
      there is no indication for the build system that this function
      should be avoided - such an indication is only given by the
      Windows App Certification Kit, which forbids using the MoveFileExA
      function.
      
      Therefore check the WINAPI_FAMILY defines instead, to figure out
      which API subset is targeted.
      Signed-off-by: NMartin Storsjö <martin@martin.st>
      8ebf02f8