3 ms·

Uh oh, I have been putting a lot of effort embedding Chromium with Qt (which does not AFAIK have a clang build). I am afraid this is really going to slow me dow

Uh oh, I have been putting a lot of effort embedding Chromium with Qt (which does not AFAIK have a clang build). I am afraid this is really going to slow me down. I wonder how this will harm other developers using CEF [0] w/ MSVC. 0 - https://bitbucket.org/chromiumembedded/cef https://bitbucket.org/chromiumembedded/cef Edit: Now that I think about it, the Qt stuff is all in shared libs, so less worried there. But with CEF, the C++ wrapper is statically linked. What is MSVC's linker's ability to consume clang objs and vice versa I wonder. If not an issue, maybe I'm just fine.

to3m 9y ago
I did a CEF-based project last year. I didn't built Chromium myself; I used a pre-build copy, from Spotify I think. The CEF build process sets this all up for you, so I expect this is typical. So this should mean that provided the clang builds of Chromium look the same to the outside world as the VC++ builds of Chromium, there won't be a problem. (It works well. The PDB files and the corresponding source code are available, so you can step through the Chromium code in Visual Studio and so on.) CEF is built as part of your program using whatever compiler you're using. I don't know what the mechanics of it are... I assume it uses the Chromium stuff via an import library? I didn't look very closely at this aspect of it.
- kodablah 9y ago
  Right, but CEF uses cmake w/ msvc customizations IIRC. And the spotify builds do ship with the DLLs already built. I asked on the CEF forum just now, we'll see.
sunnyps 9y ago
Chromium will continue using link.exe as the linker even after migrating to clang-cl. See the bottom of the email that's linked.
mwcampbell 9y ago
CEF goes to great pains to export a stable C ABI, not a C++ one, from the DLL. So I think you'll be fine.
rasjani 9y ago
Qt5.9 comes with windows clang spec for qmake. Previously you could setup it on your own in windows and Linux wasnt probably that hard either. For OS X "clang" was always a default.

to3m 9y ago

I did a CEF-based project last year. I didn't built Chromium myself; I used a pre-build copy, from Spotify I think. The CEF build process sets this all up for you, so I expect this is typical. So this should mean that provided the clang builds of Chromium look the same to the outside world as the VC++ builds of Chromium, there won't be a problem. (It works well. The PDB files and the corresponding source code are available, so you can step through the Chromium code in Visual Studio and so on.) CEF is built as part of your program using whatever compiler you're using. I don't know what the mechanics of it are... I assume it uses the Chromium stuff via an import library? I didn't look very closely at this aspect of it.

kodablah 9y ago
Right, but CEF uses cmake w/ msvc customizations IIRC. And the spotify builds do ship with the DLLs already built. I asked on the CEF forum just now, we'll see.

sunnyps 9y ago

Chromium will continue using link.exe as the linker even after migrating to clang-cl. See the bottom of the email that's linked.

mwcampbell 9y ago

CEF goes to great pains to export a stable C ABI, not a C++ one, from the DLL. So I think you'll be fine.

rasjani 9y ago

Qt5.9 comes with windows clang spec for qmake. Previously you could setup it on your own in windows and Linux wasnt probably that hard either. For OS X "clang" was always a default.