Assimp动态链接报错LNK1136问题求助（C++/DirectX11）

Hey there, sorry to hear you're stuck on this Assimp dynamic linking problem—let's walk through some targeted fixes since your static linking works, which means your core project setup is solid. The Error LNK1136 invalid or corrupt file usually points to a mismatch or broken dynamic library file/configuration. Here's what to check:

• Verify Assimp's Dynamic Library Build & Integrity
  First, make sure you're using the correct dynamic library files. If you compiled Assimp yourself, double-check that you enabled the BUILD_SHARED_LIBS flag in CMake—this generates the dynamic import library (.lib) and corresponding .dll instead of static libraries. If you downloaded prebuilt binaries, ensure you grabbed the dynamic package (not static) that matches your project's architecture (x86/x64) and Visual Studio version. A common mistake is using a static .lib file for dynamic linking, which will throw this corrupt file error. If you suspect the file is damaged, recompile or redownload Assimp's dynamic build.

• Align Project Linker Settings with Dynamic Library
  In your Visual Studio project properties:

  • Go to Linker > Input > Additional Dependencies and confirm you're adding the dynamic import library (e.g., assimp-vc143-mt.lib for Release, assimp-vc143-mtd.lib for Debug). Static libraries typically have an -s suffix like assimp-vc143-mt-s.lib—avoid these for dynamic linking.
  • Check Linker > General > Additional Library Directories points to the folder containing the correct dynamic import library, not the static library directory.

• Match C++ Runtime Library Settings
  Dynamic linking requires your project and Assimp to use the same C++ runtime library. For example:

  • If Assimp was compiled with Multi-threaded DLL (/MD) (Release) or Multi-threaded Debug DLL (/MDd) (Debug), set your project's C/C++ > Code Generation > Runtime Library to the corresponding option. Mismatched runtimes (like using MT/MTd for your project with an MD-built Assimp) can cause unexpected file corruption errors during linking.

• Fix File Path & Permission Issues
  Windows file permissions or non-standard path characters (like Chinese, spaces, or special symbols) can prevent the linker from reading the library file correctly. Try copying the Assimp dynamic import library directly into your project's output directory, or ensure the path to the library folder is free of special characters. Also, make sure your Visual Studio instance has read access to the library file's location.

• Validate DLL and Import Library Version Match
  Even if you're in the linking phase, a mismatch between the import library (.lib) and the corresponding .dll can trigger this error. Ensure both files come from the same Assimp build (same version, architecture, and VS toolset). Once linking succeeds, don't forget to place the assimp.dll (or assimpd.dll for Debug) in your executable's directory or a system-wide path for runtime execution.

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