EWDK 1703中printf所属库及链接libcurtl.lib仍遇未解析符号问题

In the EWDK 1703 (corresponding to Windows 10 Version 15063, Creators Update), the printf function (which is actually an alias for the underlying _printf in the Windows CRT) lives in the Universal C Runtime (UCRT) libraries. Here's the breakdown based on your build type:

• Static release builds: libucrt.lib
• Static debug builds: libucrtd.lib
• Dynamic release builds: ucrt.lib (links against the runtime DLL ucrtbase.dll)
• Dynamic debug builds: ucrtd.lib (links against ucrtbased.dll)

You’ll find these libraries under the EWDK’s lib\ucrt\<architecture> directory (e.g., C:\EWDK\10.0.15063.0\lib\ucrt\x86 for 32-bit targets).

First up, it looks like there’s probably a typo in your library name—libcurtl.lib is almost certainly libucrt.lib (the static UCRT library) you meant to link. Let’s walk through the most reliable fixes for this issue:

• Match CRT version and architecture to your build
  Debug builds require the debug CRT library (libucrtd.lib), while release builds use the release version (libucrt.lib). Also, double-check you’re using the library for your target architecture (x86 vs x64)—a 32-bit project can’t use a 64-bit library, and vice versa.

• Avoid conflicting CRT library links
  If your project accidentally links multiple CRT versions (e.g., both libcmt.lib and libucrt.lib), this can trigger symbol conflicts or unresolved references. Head to your linker settings and ensure only one CRT library is listed in "Additional Dependencies".

• Verify project path configurations

  1. Under C/C++ > General in project properties, add the EWDK’s UCRT header directory to "Additional Include Directories" (e.g., C:\EWDK\10.0.15063.0\include\ucrt).
  2. Under Linker > General, add the corresponding UCRT library directory to "Additional Library Directories" (e.g., C:\EWDK\10.0.15063.0\lib\ucrt\x86).
  3. Double-check "Additional Dependencies" under Linker > Input for typos in the library name.

• Check for macro-driven function redirection
  If your project defines _UNICODE or UNICODE, some CRT functions get redirected to their wide-character counterparts (like _wprintf instead of _printf). If you’re calling the ANSI versions but these macros are active, you’ll hit unresolved symbols. Either switch to wide-character function calls or remove the unicode macros if you don’t need them.

• Confirm EWDK installation integrity
  Missing library files can cause this issue too. Navigate to the UCRT library directory in your EWDK setup and make sure libucrt.lib (or libucrtd.lib) exists. If it’s missing, repair or re-download the EWDK 1703 package.

• Try specifying the full library path
  If the linker isn’t picking up the library from the additional directories, add the full path to the library in "Additional Dependencies" (e.g., C:\EWDK\10.0.15063.0\lib\ucrt\x86\libucrt.lib).

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