Fatal error LNK1104: cannot open file 'gdi32.lib'

Question

Every time I try to run my code I get this error. I\'ve tried everything, installing the SDK, but I still get the same error.

1>------ Build started: Proj         


        

Answer 1

If you have moved the code from another computer, it may be using the wrong SDK on your platform. Check project Properties → General → Windows SDK Version and set it to something shown in the list.

Answer 2

To solve it you will need to locate a folder containing the gdi32.lib file.

For my system I found it in C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10240.0\um\x86.

Simply add it into the property sheet for your project. As described in other posts, menu Project → Properties then VC++ directories. Add the path at the top.

Answer 3

If anyone has this problem on Visual Studio 2017, it is an issue with the Windows 10 Creators Update.

A workaround is to select the "Windows 10 SDK (10.0.15063.0) for Desktop C++ x86 and x64" under the "Desktop development with C++" workload in the Visual Studio Installer.

https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes#KINativeDesktopWorkload

Answer 4

In Visual Studio 2017 (Community edition) I solved this by switching the Windows SDK version in the project properties from 10.0.10586.0 to 10.0.16299.0 (which is the version I've installed on my machine).

Here is how:

1. In Visual Studio, go to project properties:

2. Choose an installed SDK version:

Reference: the developer community for VS

Answer 5

I'm on Windows 8.1 Visual Studio 2017 Professional, and I got it to work after switching the project properties Windows SDK version to 8.1, build, then switch it back to 10.0.16299.0.

I was trying to compile the CUDA sample project.

It worked, don't ask me why. Maybe it has something to do with me having the Visual Studio Community 2017 and then uninstalling it to install the professional.

Answer 6

For those having the same problem with Visual Studio 2015 on Windows 10, it may be because the installation was broken. If so, just launch the installation program to do "Repair".

It may be a good idea to install the Visual Studia 2015 Update 1 RC too.

It worked for me...