Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a library written in ISO C++. It doesn’t use Winapi, TCHAR or anything like that. I’m currently building it as a static library with character set set to Unicode. I intend to link it to other libraries, some of them built using Unicode, some – MBCS.
Do I need to create two configurations and build two versions (MBCS and Unicode) in this case?
This is not a problem. Code that uses utf-16 encoded Unicode strings uses wchar_t*, code that uses a legacy 8-bit encoding uses char*. Unambiguous both to the compiler and linker. The only reason the setting exists is because Windows headers and the non-standard
<tchar.h>contain macros that translate a typedef (like TCHAR) to either of those strings types, guided by the UNICODE and _UNICODE #defines.Of course, using this library from a program that uses char* for strings will be an enormous pita. The program must translate the strings, note that a cast won’t do.