microsoft / microsoft/DirectX-Graphics-Samples
HelloVADecode , HelloVAEncode, and HelloVAResourceInterop fail to build with included solution file
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.8k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
D3D12HelloWorld.sln included with the package appears to be missing the lib folder from Microsoft.Direct3D.VideoAccelerationCompatibilityPack.1.0.0 which contains the va.lib and va_win32.lib
error: "LNK2001 unresolved external symbol vaDestroyConfig"
VideoAccelerationCompatibilityPack NuGet package was already installed for the 3 projects.
Simply adding "va.lib;va_win32.lib" to linker "Additional Dependencies" in each of the projects worked.
Not sure if that is the recommended way your team is handling linker flags, otherwise I would create a PR.
Test Setup:
- VS 2022 Community Edition + Windows 11 "Next" SDK + target v143
Introduced from #810 @sivileri
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
Open D3D12HelloWorld.sln and inspect the linker settings for HelloVADecode, HelloVAEncode, and HelloVAResourceInterop, along with the Microsoft.Direct3D.VideoAccelerationCompatibilityPack.1.0.0 package contents. Reproduce the unresolved vaDestroyConfig error, then verify that the three projects build successfully with the required va.lib and va_win32.lib dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, computer-graphics
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100