microsoft / microsoft/FFmpegInterop
FFmpeg Windows 8.1 build broken for submodule version after origin/master
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Description
Following the WinRT build instructions, the Windows 8.1 build fails for commits after the current origin/master (69fd3e210f18feee9af1c2da02db7bfc57289ee6). When building with the next commit that changes the submodule (3ed71292fde5828dc998ebe4dbd53b05a2be1d56), the Windows 8.1 build breaks with the following messages:
hwcontext_d3d11va.o : error LNK2019: unresolved external symbol CreateMutex referenced in function d3d11va_device_init
libavutil/avutil-55.dll : fatal error LNK1120: 1 unresolved externals
make: *** [/c/records/projects/ffmpeginterop/FFmpegInterop/ffmpeg/ffbuild/library.mak:102: libavutil/avutil-55.dll] Error 96
I realize that this is an FFmpeg issue and not FFmpegInterop, but was unsure whether it was the WinRT build instructions that needed to be updated. Let me know if I should post this somewhere else.
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows 8.1 WinRT build using the current origin/master submodule and commit 3ed71292fde5828dc998ebe4dbd53b05a2be1d56. Start with the hwcontext_d3d11va.o linker error and the link step in ffbuild/library.mak; done means the build succeeds or the required instruction change is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100