Recherche avancée

Sur d’autres sites (9906)

• configure : disable the new optimizer in Visual Studio 2015 Update 3

  28 juin 2016, par Hendrik Leppkes

  configure : disable the new optimizer in Visual Studio 2015 Update 3
  Visual Studio 2015 Update 3 introduced a new SSA optimizer, however
  
  it unfortunately causes miscompilations. Until it is fixed, the new
  
  optimizations are disabled and should be re-checked on subsequent
  
  compiler releases.
  Fixes recent FATE failure of fate-lavf-pam on VS2015.
  

  • [DH] configure

• ffmpeg compilation error in windows 10 x64 for Visual Studio 2015 CE

  12 avril 2016, par Anqush

  So i was trying to use FFmpegInterop for win10 UWP application. And followed the specification given on https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT.

  here is some environment information :

  VS2015 Community Edition with 10.0.10240.0 SDK

  OS : Windows 10 Enterprise x64

  PATH were set to:Program Files (x86)/Microsoft Visual Studio 14.0/VC/BIN/x64_ARM

  So when i did this in msys2_shell.bat

  ../../../configure \
  
  --toolchain=msvc \
  
  --disable-programs \
  
  --disable-d3d11va \
  
  --disable-dxva2 \
  
  --arch=x86_64 \
  
  --enable-shared \
  
  --enable-cross-compile \
  
  --target-os=win32 \
  
  --extra-cflags="-MD -DWINAPI_FAMILY=WINAPI_FAMILY_APP -D_WIN32_WINNT=0x0A00" \
  
  --extra-ldflags="-APPCONTAINER WindowsApp.lib" \
  
  --prefix=../../../Build/Windows10/x64

  I got a warning regarding some pkg file that can’t be found and may cause library detection issues.

  For then i ignored it. After that i entered

  make

  this started a series of processing in which there is a lot of possibly harmful warnings. Like :-

  c:\ffmpeginterop\ffmpeg\libavcodec\get_bits.h(307): warning C4101: 're_cache': unreferenced local variable
  
  CC libavformat/srtdec.o
  
  srtdec.c
  
  c:\ffmpeginterop\ffmpeg\libavutil\libm.h(438): warning C4211: nonstandard extension used: redefined extern to static
  
  c:\ffmpeginterop\ffmpeg\libavformat\subtitles.h(189): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data

  So my question is that. Is this dangerous to proceed with. Can you help me for i should proceed with my project without any worry or not ? And i would be gratefull if anyone can guide me to watc out for specific errors that this could generate.

  I know this is a lot to ask. But i would be gratefull.
  Thanks

  Edit : Now i cant run the samples included in the ffmpeginterop package. The sample project wont debug. saying these are out of date.

• Unresolved external symbol when linking ffmpeg/avcodec with Visual Studio 2015 ?

  2 décembre 2015, par Ragnar

  I’m trying to build ffmpeg/avcodec library with Visual Studio 2015 and it gives me following linking error :

  allcodecs.obj : error LNK2001: unresolved external symbol ff_h263_vaapi_hwaccel 
  
  allcodecs.obj : error LNK2001: unresolved external symbol ff_h263_vdpau_hwaccel
  
  allcodecs.obj : error LNK2001: unresolved external symbol ff_h263_videotoolbox_hwaccel
  
  ...

  The problem comes from this macro https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/allcodecs.c#L34

  #include "config.h"
  
  #include "avcodec.h"
  
  #include "version.h"
  
  
  
  ...
  
  
  
  #define REGISTER_HWACCEL(X, x)                                      \
  
      {                                                               \
  
          extern AVHWAccel ff_##x##_hwaccel;                          \
  
          if (CONFIG_##X##_HWACCEL)                                   \
  
              av_register_hwaccel(&ff_##x##_hwaccel);                 \
  
      }
  
  
  
  ...
  
  
  
  void avcodec_register_all(void)
  
  {
  
      static int initialized;
  
  
  
      if (initialized)
  
          return;
  
      initialized = 1;
  
  
  
      /* hardware accelerators */
  
      REGISTER_HWACCEL(H263_VAAPI,        h263_vaapi);
  
      REGISTER_HWACCEL(H263_VIDEOTOOLBOX, h263_videotoolbox);
  
      ...

  I don’t understand why do these methods even get declared when my config has them set to 0

  #define CONFIG_H263_VAAPI_HWACCEL 0
  
  #define CONFIG_H263_VDPAU_HWACCEL 0
  
  #define CONFIG_H263_VIDEOTOOLBOX_HWACCEL 0
  
  ...

  Btw it builds OK when I use msys/make tooling.