magreenblatt wrote:That should be fine from a design perspective, if not ideal from a security perspective.
Well, using Qt linked as shared libs on windows means you basically have to use dynamic CRT (/MD) which forces us to turn off the sandbox, unfortunately. we haven't yet found a way around this. Would switching to clang help in this regard?
magreenblatt wrote:CEF/Chromium don't run V8 in the main process so there shouldn't be any runtime conflicts.
Thanks, good to know.
I looked at at least exposing the v8 symbols in libcef.dll. I mean, I'm sure it'd possible to at least make them visible with enough work on the .gn files, but I noticed symbols like "std::Cr::unique_ptr" which seem come from the customized libcxx inside chrome. Wouldn't these be totally incompatible with regular C++ code that links with a standards-compilant runtime? Was this customized libcxx the reason why the C++ => C => C++ bridge, or classes like CefString became necessary?
If yes, then there really doesn't seem to be any practical way to talk to v8 directly inside the libcef.dll.