1. 28 Nov, 2018 1 commit
  2. 09 Apr, 2018 1 commit
    • wm4's avatar
      w32pthreads: always use Vista+ API, drop XP support · c7ab6aff
      wm4 authored
      This removes the XP compatibility code, and switches entirely to SRW
      locks, which are available starting at Windows Vista.
      
      This removes CRITICAL_SECTION use, which allows us to add
      PTHREAD_MUTEX_INITIALIZER, which will be useful later.
      
      Windows XP is hereby not a supported build target anymore.
      Signed-off-by: 's avatarDiego Biurrun <diego@biurrun.de>
      c7ab6aff
  3. 27 Feb, 2018 1 commit
  4. 07 Jan, 2018 1 commit
  5. 26 Dec, 2017 2 commits
  6. 20 Nov, 2017 1 commit
  7. 17 Nov, 2017 1 commit
  8. 16 Nov, 2017 1 commit
  9. 07 Nov, 2017 1 commit
  10. 25 Oct, 2017 1 commit
  11. 12 Oct, 2017 1 commit
  12. 31 Aug, 2017 2 commits
  13. 30 Aug, 2017 1 commit
  14. 30 Jul, 2017 1 commit
    • Matt Oliver's avatar
      win32_dlfcn: Support WinRT/UWP. · a3833bee
      Matt Oliver authored
      This only enables dlls that are packaged with the application to be
      loaded. Due to the limitations of WinRT/UWP it is not allowed to load
      external/system dlls so this cannot be used as a complete replacement
      for normal win32 dll loading.
      Signed-off-by: 's avatarMatt Oliver <protogonoi@gmail.com>
      a3833bee
  15. 01 Jun, 2017 1 commit
  16. 15 May, 2017 2 commits
  17. 09 May, 2017 3 commits
  18. 04 May, 2017 1 commit
  19. 13 Apr, 2017 1 commit
    • Aaron Levinson's avatar
      Support building C++ files with MSVC · bceb3d0f
      Aaron Levinson authored
      Made appropriate changes to be able to successfully
      build C++ files using a Visual C++ build on Windows.
      
      Based on an earlier patch by Kyle Schwarz.
      
      Comments:
      
      -- compat/w32pthreads.h: Made appropriate changes to w32pthreads.h to
         get it to build when it is being included in a C++ file and built
         with Visual C++.  This is mostly a copy of Kyle Schwarz's patch as
         described above.
      
      -- configure:
      a) Now calling set_ccvars CXX to cause the various CXX_ variables to
         be setup properly.  For example, with MSVC (Microsoft Visual C++),
         this causes CXX_O to be set to -Fo$@ instead of using the default
         value.  The default value does not work with Visual C++.  This
         change will also have the impact of correcting CXX_O (and possibly
         CXX_C) for other compilers, although this is really only relevant
         for the Intel compiler, in addition to MSVC.
      b) Now using cl for the C++ compiler for the MSVC toolchain.  This is
         currently only relevant for building the
         Blackmagic/Decklink-related files under avdevice.
      Signed-off-by: 's avatarHendrik Leppkes <h.leppkes@gmail.com>
      bceb3d0f
  20. 04 Apr, 2017 1 commit
  21. 02 Apr, 2017 1 commit
  22. 18 Mar, 2017 1 commit
  23. 01 Mar, 2017 1 commit
  24. 08 Dec, 2016 1 commit
    • Wan-Teh Chang's avatar
      compat/atomics: add typecasts in atomic_compare_exchange_strong() · 6a93b596
      Wan-Teh Chang authored
      The Solaris and Windows emulations of atomic_compare_exchange_strong()
      need typecasts to avoid compiler warnings, because the functions they
      call expect a void* pointer but an intptr_t integer is passed.
      
      Note that the emulations of atomic_compare_exchange_strong() (except
      the gcc version) only work for atomic_intptr_t because of the type of
      the second argument (|expected|). See
      http://en.cppreference.com/w/c/atomic:
      
      _Bool atomic_compare_exchange_strong( volatile A* obj,
                                            C* expected, C desired );
      
      The types of the first argument and second argument are different
      (|A| and |C|, respectively). |C| is the non-atomic type corresponding
      to |A|. In the emulations of atomic_compare_exchange_strong(), |C| is
      intptr_t. This implies |A| can only be sig_intptr_t.
      Signed-off-by: 's avatarWan-Teh Chang <wtc@google.com>
      6a93b596
  25. 03 Dec, 2016 1 commit
    • Diego Biurrun's avatar
      Remove Plan 9 support · 3794062a
      Diego Biurrun authored
      Supporting the system was a nice joke for the 9 release, but it has
      run its course. Nowadays Plan 9 receives no testing and has no
      practical usefulness.
      3794062a
  26. 02 Dec, 2016 6 commits
  27. 24 Nov, 2016 1 commit
  28. 22 Nov, 2016 3 commits
    • Philip Langdale's avatar
      avcodec/cuvid: Add support for P010/P016 as an output surface format · 81147b55
      Philip Langdale authored
      The nvidia 375.xx driver introduces support for P016 output surfaces,
      for 10bit and 12bit HEVC content (it's also the first driver to support
      hardware decoding of 12bit content).
      
      The cuvid api, as far as I can tell, only declares one output format
      that they appear to refer to as P016 in the driver strings. Of course,
      10bit content in P016 is identical to P010, and it is useful for
      compatibility purposes to declare the format to be P010 to work with
      other components that only know how to consume P010 (and to avoid
      triggering swscale conversions that are lossy when they shouldn't be).
      
      For simplicity, this change does not maintain the previous ability
      to output dithered NV12 for 10/12 bit input video - the user will need
      to update their driver to decode such videos.
      81147b55
    • Timo Rothenpieler's avatar
      avcodec/cuvid: use dynamically loaded CUDA/CUVID · d9ad18f3
      Timo Rothenpieler authored
      And remove the now obsolete compat headers.
      d9ad18f3
    • Timo Rothenpieler's avatar
      compat/cuda: add dynamic loader · 5c02d282
      Timo Rothenpieler authored
      5c02d282