Fix example_win32_directx11 linker settings.

[tom-seddon]

Got an error building example_win32_directx11 from the repo, using Visual Studio 2017, compiler version Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27023.1 for x86.

Running build_win32.bat I get this command line:

cl /nologo /Zi /MD /I .. /I ..\.. /I "C:\Program Files (x86)\Windows Kits\10\Include\um" /I "C:\Program Files (x86)\Windows Kits\10\Include\shared" /I "Include" /D UNICODE /D _UNICODE *.cpp ..\imgui_impl_dx11.cpp ..\imgui_impl_win32.cpp ..\..\imgui*.cpp /FeDebug/example_win32_directx11.exe /FoDebug/ /link /LIBPATH:"/Lib/x86" d3d11.lib d3dcompiler.lib

And this error:

imgui_impl_win32.obj : error LNK2019: unresolved external symbol __imp__GetDeviceCaps@8 referenced in function "float __cdecl ImGui_ImplWin32_GetDpiScaleForMonitor(void *)" (?ImGui_ImplWin32_GetDpiScaleForMonitor@@YAMPAX@Z)
Debug/example_win32_directx11.exe : fatal error LNK1120: 1 unresolved externals

The fix for me was to add gdi32.lib to the command line explicitly.

Thanks,

--Tom

[ocornut]

Hello @tom-seddon,

I noted this only happens in the docking branch, due to the presence of ImGui_ImplWin32_GetDpiScaleForMonitor() calling GetDeviceCaps(), and this affect all the examples using imgui_impl_win32.cpp (not only the DX11 one).

I added the extra gdi32.lib linkage request through pragma, as commonly/conventially allowed by Visual Studio compiler.

[ice1000]

Hi, the unresolved reference still happens to me. Applying this PR fixes the issue.