Advertisement

N00B Q: VS2017 refuses to resolve D3D12GetDebugInterface

Started by March 29, 2018 06:29 AM
3 comments, last by SoldierOfLight 6 years, 10 months ago

Hi all,

I did a lot of work years ago with earlier DX9/10.  I haven't touched code since and so I thought I might get up to speed with the DirectX 12 changes while I have a ton of spare time.

So, I installed VS2017 CE and started following along with a YouTube lesson set.  Win10 is fully updated and VS2017 is trying to build for 10.0.16299.  The Graphic Tools FoD is also installed (many times).

I'm sure this is my fault and probably a really dumb C++ 101 issue, but if anyone could help me provide relevant diagnosis information to get a solution, I would be very appreciative.

Thanks!

Matt

UnresolvedSymbols.PNG

Are you linking against D3D12.lib? :)

Right click your project in Solution Explorer, Properties, Linker, and Command Line and see if you have that lib there.

Advertisement

Told you it was a n00b question!  Thank you, thank you, thank you!

I don't recall having to explicitly add libraries before (it's been a lonnng time though).  Proposed solution worked like a charm.

For others:  

As PCMaster said, if the D3D12.lib isn't listed in the /DYNAMICBASE parameters in the section PCMaster described, just add it under to

Right click your Project in Solution Explorer, Properties

Then Linker -> Input -> Additional Dependencies

Thanks again PCMaster! :) 

 

For what it's worth, you can also put:


#pragma comment(lib, "d3d12.lib")

into a file in your project, which would have the same effect.

This topic is closed to new replies.

Advertisement