after beginning problem which i could solve, now i have the dlls i need (ceflib.dll and other).
But this time im facing some new issues with strings, when i try to assign CefString to CString i get errors i never had before and our implementation is from 2018, current CEF Version is the 112 branch 5615 build.
When i assign value from CefString to CString MFC, i never get any errors, but now i get the error:
"error C2679: binary '=': no operator found which takes a right-hand operand of type 'const char16_t *' (or there is no acceptable conversion)"
My current SDK installed:
Windows SDK 10.0.18362.1
Windows SDK 10.0.19041.685
Windows SDK 10.0.20348.1
Windows SDK 10.0.22000.832
Windows SDK 10.0.22621.1778
Windows SDK 10.0.22621.2428
I understand the error, but i dont understand why is comming now for first time after 2018 without changing our code. Our build process is also the same and is from the automated build steps which works before always.
Our current version is the 112 from branch 5615, so my question is are there any changes related to CefString since version 112 branch 5615? Or did i build with some flags without noticing it
I build CEF as 32bit output
Here is a simple example which describes my question ( i removed redundant code and let only that for example):
- Code: Select all
void CCefTabCtrl::OnIpcMessage(CefRefPtr<CefProcessMessage> message)
{
CefString strJson;
if (arguments->GetSize() >= 2)
strJson = arguments->GetString(1);
// Structure with some numeric and string fields as CString like CString strJsonParam;
CefCallbackThreadInfo* pInfo = new CefCallbackThreadInfo();
pInfo->strJsonParam = strJson.c_str(); // THIS LINE FAILS NOW
// but this works:
pInfo->strJsonParam = strJson.ToWString().c_str(); // BUT THIS WORKS
}
One short example which i tested on the cefclient app with same error:
- Code: Select all
CString csMFCString;
CefString cefString = "Test content";
csMFCString = cefString.c_str(); // WORKS with 112 on branch 5615 but now i get the error above
csMFCString = cefString.ToWideString().c_str(); // THIS WORKS no errors with version 118 and branch 5993
Any hint for this behaviour, did anyone facing same or similar issue?
Thanks for any input
regards
miro