Recherche avancée

Sur d’autres sites (7855)

• Chromium Build Failed on Windows:D3D Compiler DLL (\third_party\angle\src)

  31 mars 2016, par Vish

  I have followed same step mentioned in this question. Few extra flag I have set get propriety FFMPEG codec. Its failing every time, with following logs.

  [233/19712] ACTION Copying D3D Compiler DLL...
  
  FAILED: F:\Chrome\depot_tools\python276_bin\python.exe gyp-win-tool action-wrapper environment.x86 copy_compiler_dll_target_copy_dll_a30e198148542d4bce19a5c818c6884f..rsp ..\..\third_party\angle\src
  
  [233/19712] CC obj\third_party\icu\source\stubdata\icuuc.stubdata.obj
  
  ninja: build stopped: subcommand failed.

  For FFMPEG using following set command :

  set GYP_DEFINES=branding=Chromium buildtype=Official component=shared_library disable_nacl=1 enable_automation=0 enable_captive_portal_detection=0 enable_google_now=0 enable_hidpi=0 fastbuild=1 ffmpeg_branding=Chrome incremental_chrome_dll=0 proprietary_codecs=1 remoting=0

  My System Information Details :

  Windows 10 64 Bit 8 GB RAM. Trail Version of Visual Studio 2015
  Installed, but now it is expired. Now I have installed Community
  Version 2013 update 4.

  Does it effect both version effect the execution ? Checked in path, its using Window Kit 8.1. What other part should I check for successful execution ?

• OpenCV ffmpeg DLL not loaded when running app on Windows 7, works on 8 and 10

  2 novembre 2016, par David G.

  I need to maintain a desktop app written in C++, using Qt and OpenCV for some video processing. As far as I understood, the decoding part of OpenCV is delegated to ffmpeg in a separate DLL for licensing reasons.

  The development environment is on Windows 10, using QT Creator and MSVC12 64-bit as compiler. OpenCV version is 3.0, the official distribution. Here, everything runs fine, I am able to decode a video using VideoCapture::open().

  Issues arise when I try to run the application in a standalone fashion with all the required DLLs in the same folder as the .exe file. All cases below are 64-bit OSes.

  On a Windows 10 computer, not the same as the developement machine and no developer libraries present, the video decoding works fine. I have tested on a Windows 8 machine as well, no issues so far.

  On Windows 7, the things get tricky. The same video files that successfully load during the previous tests are not recognized by the app at all i.e. the isOpened call on VideoCapture returns false. For further testing, I stripped the opencv_ffmpeg300_64.dll file to narrow down the issue on Windows 10 and 8 ; as expected, without this DLL the app is no more able to open the same video files.

  It seems that the DLL is simply not recognized on Windows 7.

  Edit : Further investigation using Process Explorer clearly shows that the aforementioned DLL is not loaded when the app runs on Windows 7.

  • Is there something specific about how Windows 7 manages the DLL path resolution and eventual security measures ? Seems normal that the first search location is the same folder as the executable, which is the case here.

  I have tried to trace using WinApiOverride32, with no results.

• OpenCV ffmpeg DLL not loaded when running app on Windows 7, works on 8 and 10

  4 avril 2018, par David G.

  I need to maintain a desktop app written in C++, using Qt and OpenCV for some video processing. As far as I understood, the decoding part of OpenCV is delegated to ffmpeg in a separate DLL for licensing reasons.

  The development environment is on Windows 10, using QT Creator and MSVC12 64-bit as compiler. OpenCV version is 3.0, the official distribution. Here, everything runs fine, I am able to decode a video using VideoCapture::open().

  Issues arise when I try to run the application in a standalone fashion with all the required DLLs in the same folder as the .exe file. All cases below are 64-bit OSes.

  On a Windows 10 computer, not the same as the developement machine and no developer libraries present, the video decoding works fine. I have tested on a Windows 8 machine as well, no issues so far.

  On Windows 7, the things get tricky. The same video files that successfully load during the previous tests are not recognized by the app at all i.e. the isOpened call on VideoCapture returns false. For further testing, I stripped the opencv_ffmpeg300_64.dll file to narrow down the issue on Windows 10 and 8 ; as expected, without this DLL the app is no more able to open the same video files.

  It seems that the DLL is simply not recognized on Windows 7.

  Edit : Further investigation using Process Explorer clearly shows that the aforementioned DLL is not loaded when the app runs on Windows 7.

  • Is there something specific about how Windows 7 manages the DLL path resolution and eventual security measures ? Seems normal that the first search location is the same folder as the executable, which is the case here.

  I have tried to trace using WinApiOverride32, with no results.