The linker keeps complaining after I changed from legacy DirectX SDK to Windows SDK (Visual Studio 2015))

Question

I just removed all of the headers that were included in the DirectX SDK and i moved towards the Windows SDK, but once I did, the linker constantly complains about an \"unresolve

Answer 1

"Unresolved symbol" means that either you directly call these functions, or they are called by functions that you are calling. Functions that you call must either be defined by source code that you compile and link into your application, or they must be defined by libraries that you link into your application.

The DirectX Math library is completely defined in the header; there is no library to link against. Their definitions are in the various DirectX Math .inl files that are included by DirectXMath.h.

In other words, it's virtually impossible for you to include the header file declaring these functions and not get the implementation for them.

Since I am not at your computer, I can't tell you exactly what you did to cause this state of affairs. To determine the actual cause, you should simplify the problem to the smallest possible program that reproduces the problem, such as creating a new project that only includes DirectXMath.h and uses the function XMVectorMultiply to perform a vector multiplication and print the result.

Once you get that simple program working, then compare it to your program and look at the differences to find the source of your error.

This is the same process you go through when debugging an application at runtime, it's just that you're debugging your build instead of your application.