Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ffmpeg[ffmpeg]:x64-windows] compiles the executable but it won't open #12008

Closed
ivanovmp opened this issue Jun 18, 2020 · 0 comments · Fixed by #12063
Closed

[ffmpeg[ffmpeg]:x64-windows] compiles the executable but it won't open #12008

ivanovmp opened this issue Jun 18, 2020 · 0 comments · Fixed by #12063
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@ivanovmp
Copy link

The bug
After installing ffmpeg with the option ffmpeg, vcpkg creates several executables. However, none of them can be opened because of absence of necessary DLL's.

Environment

  • OS: 64-bit Windows 10 (Russian language)
  • Compiler: Microsoft ® C/C++ Optimizing Compiler Version 19.26.28612 for x64.

To Reproduce
Steps to reproduce the behavior:

  1. ./vcpkg install ffmpeg[ffmpeg]:x64-windows
  2. We get ./buildtrees/ffmpeg/x64-windows-dbg/ffmpeg.exe, ./buildtrees/ffmpeg/x64-windows-rel/ffmpeg.exe, ./installed/x64-windows/debug/tools/ffmpeg.exe, ./installed/x64-windows/tools/ffmpeg.exe, ./packages/ffmpeg_x64-windows/debug/tools/ffmpeg.exe, ./packages/ffmpeg_x64-windows/tools/ffmpeg.exe
  3. After execution each of them throws an error message box telling me that the executable cannot run because it hasn't found avdevice-58.dll

Expected behavior
I expect at least one of these ffmpeg.exes to just execute without running into problems. Maybe vcpkg should have put the necessary DLL's into some common directory for libraries or into direct reach of these .exes. It's strange to build ffmpeg.exe and leave it in the state in which it wouldn't work. After I copied all the needed DLL's into the directory containing ffmpeg.exe it was able to open, but maybe this task is to be done by vcpkg?

@LilyWangL LilyWangL added the category:port-bug The issue is with a library, which is something the port should already support label Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants