Cannot convert from 'const char [..]' to 'LPCTSTR'

最新推荐文章于 2021-05-18 20:21:35 发布

dadalan

最新推荐文章于 2021-05-18 20:21:35 发布

阅读量3.6k

点赞数

分类专栏： windows 文章标签： properties compiler character compilation microsoft function

本文链接：https://blog.csdn.net/dadalan/article/details/3958116

版权

windows 专栏收录该内容

96 篇文章

订阅专栏

当尝试编译包含`MessageBox("Hello world!");`的代码时，出现错误C2664，表明在使用多字节字符串(const char [12])调用期望接收宽字符(LPCTSTR)的函数。解决方案包括更改项目配置以使用多字节字符串或通过前缀L或_T宏指定字符串的特定编码。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Question

I'm trying to compile a piece of code such as:

MessageBox("Hello world!");

... when I compile the project, the compiler yields:

error C2664: 'CWnd::MessageBoxW' : cannot convert parameter 1 from 'const char [12]' to 'LPCTSTR'

What am I doing wrong?

Problem

This error message means that you are trying to pass a multi-byte string (const char [12]) to a function which expects a unicode string (LPCTSTR). The LPCTSTR type extends to const TCHAR*, where TCHAR is char when you compile for multi-byte and wchar_t for unicode. Since the compiler doesn't accept the char array, we can safely assume that the actual type of TCHAR, in this compilation, is wchar_t.

Resolution

You will have to do one of two things:

Change your project configuration to use multibyte strings. Press ALT+F7 to open the properties, and navigate to Configuration Properties > General. Switch Character Set to "Use Multi-Byte Character Set".
Indicate that the string literal, in this case "Hello world!" is of a specific encoding. This can be done through either prefixing it with L, such as L"Hello world!", or surrounding it with the generic _T("Hello world!") macro. The latter will expand to the L prefix if you are compiling for unicode (see #1), and nothing (indicating multi-byte) otherwise.

Variations

Another error message, indicating the same problem, would be:

cannot convert parameter 1 from 'const char [12]' to 'LPCWSTR'

Where LPCWSTR maps to a wchar_t pointer, regardless of your build configuration. This problem can be resolved primarily by using solution #2, but in some cases also #1. A lot of the Microsoft provided libraries, such as the Platform SDK, have got two variations of each function which takes strings as parameters. In case of a unicode build, the actual functions are postfixed W, such as the MessageBoxW seen above. In case of multi-byte, the function would be MessageBoxA (ASCII). Which of these functions is actually used when you compile your application, depends on the setting described in resolution #1 above.