unicode vs multibyte

[bishopnator]

Hello, I am trying to integrate your library into my project, but I
got several compilation errors in CrashRptProbe project related to my
mutlibyte settings. All my projects uses multibyte character set so I
changed it also in CrashReport library, but it seems, that there are
some problems. Could you verify this? The problem is about using
CString from atlmisc.h which is adapted according to current character
set while in xxxW functions it is necessary to use something like
CStringW in MFC lib (so forcing usage of proper version of the
CString). If it would be possible to make it as part of the CMake
process for generating vcproj files, it would be really great.

[zexspectrum]

Hello, it is not recommended to modify character set settings in CrashRpt solution projects. CrashRpt should be always compiled using the UNICODE character set. In your multi-byte application, you can use A-suffixed functions from CrashRpt API. For example, use crInstallA(), crAddFile2A() and so on. Typically, you use a character-set-independent mapping of a function name, for example crInstall() expands into crInstallA() in a multi-byte program, and into crInstallW() in a wide-char prorgam. For more info, see this page  http://crashrpt.sourceforge.net/docs/html/using_crashrpt_api.html