3 ms·
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 y
by 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 agoRight, 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.