使用VS2019编译C++遇LINK错误：无法打开kernel32.lib求助

Hey there, let's sort out that LNK1104 error you're running into with cl file.cpp. This is a common issue when using MSVC's compiler without setting up the correct environment variables first, and it doesn't require moving your code to the same drive as the compiler—so no need to worry about disk space constraints. Here's how to fix it:

1. Use the Visual Studio Developer Command Prompt (Easiest Fix) #

The simplest way is to use the dedicated command prompt that comes with Visual Studio 2019. This prompt automatically configures all the necessary environment variables for the compiler, linker, and Windows SDK libraries (including where kernel32.lib lives).

• Open your Start Menu, navigate to the "Visual Studio 2019" folder.
• Choose the appropriate prompt for your target platform:
  • x64 Native Tools Command Prompt for VS 2019 (for 64-bit builds)
  • x86 Native Tools Command Prompt for VS 2019 (for 32-bit builds)
• Once the prompt is open, navigate to your code's directory (on your large drive) and run cl file.cpp again—it should work without the linker error.

2. Manually Configure Environment Variables (For Regular Command Prompts or VS Code) #

If you prefer using a regular command prompt or VS Code's integrated terminal, you can use MSVC's vcvarsall.bat script to set up the environment manually.

• First, find the path to vcvarsall.bat for your VS 2019 installation. It's usually located at:

  C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat
  

  (Adjust the path if you installed VS in a different location or use a different edition like Professional)
• Open your command prompt or VS Code terminal, run the script with your target platform:

  "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" x64
  

  (Replace x64 with x86 if you need 32-bit builds)
• Now, navigate to your code directory and run cl file.cpp—the linker will find kernel32.lib because the script added the Windows SDK library paths to your LIB environment variable.

3. Set Up VS Code Tasks to Automate the Environment #

If you're using VS Code for development, you can update your tasks.json to run vcvarsall.bat automatically before compiling. Here's an example task:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Compile with MSVC",
      "type": "shell",
      "command": "cmd /c \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Auxiliary\\Build\\vcvarsall.bat\" x64 && cl /EHsc file.cpp",
      "args": [],
      "group": {
        "kind": "build",
        "isDefault": true
      },
      "problemMatcher": ["$msCompile"]
    }
  ]
}

This way, every time you trigger the build task in VS Code, it will set up the correct environment and compile your code without manual setup.

A Quick Note on kernel32.lib #

You don't need to have kernel32.lib in your code directory or compiler directory—it's stored in the Windows SDK (usually in C:\Program Files (x86)\Windows Kits\10\Lib\<SDK Version>\um\<Platform>). The key is making sure your environment variables point to this location, which the developer prompt or vcvarsall.bat handles automatically.

内容的提问来源于stack exchange，提问作者jc235