The Windows SDK also don't have xnamath.h because it's been replaced by DirectXMath.ĭirectX 12 development requires the Windows 10 SDK as the legacy DirectX SDK has nothing newer than DirectX 11.0. dxsdkaug2006 Company Microsoft Corporation Description Win32 Cabinet Self-Extractor Fileversion.
Miscellaneous tools such as dxtex.exe, meshconvert.exe, texconv.exe, and uvatlas.exe can be found online. For Direct3D 11 development, there are open source replacements for that functionality: The Game Definition File Maker tool (GDFMaker.exe) is included in the x86 subdirectory under the bin folder in the Windows SDK, and supports both Windows Store apps and Win32 desktop applications. The Windows SDKs also do not have d3dx9.h, d3dx10.h, or d3dx11.h as those utility libraries are deprecated so they were not moved to the Windows SDK. and those headers/libs are *newer* than the ones shipped in even the most recent legacy DirectX SDK (June 2010). SDK does contain d3d11.h, d3d11_1.h, d3dcompiler.h, DirectXMath.h, d3d11.lib, dxgi.lib, etc. The Windows SDKs do *not* have the dxsdkver.h header because that header was only relevant to the standalone DirectX SDK. You just use the Windows 8.0 SDK, Windows 8.1 SDK, or Windows 10 SDK. There are a few specific scenarios where you do still need to use it covered in detail in this blog post:įor DirectX 11 development you don't need to use it.
The legacy DirectX SDK is end-of-life as of the June 2010 release as indicated on
0 kommentar(er)
