Hi,
It's a bit of work, yes, but define "a lot"? :) We are talking about hours, not days or weeks, so in that sense, it's fairly reasonable.
The way it's done it basically this:
- Update the cef-binary-repo (
https://github.com/cefsharp/cef-binary) with the new content from the .zip provided by the CEF project. I usually don't build CEF from source; it's too much work & time consuming, and I'm too lazy. It's usually easier for me to just grab the .zip-ball from Marshall and use it.
- Change the compilation flags (so that we use a multi-threaded DLL version of the C/C++ MS runtime).
- Rebuild the libcef-dll-wrapper stuff, and copy the .lib file into the proper place (+ the .dll files). This part is a bit cumbersome, and we should perhaps try to streamline it. Then again, it's not that it happens that often (at least in our case - perhaps it would be yours, in which case streamlining wouldn't be such a bad idea). The problem here is that the complexity grows as we want to support more and more platforms. Right now, we have VS2010, VS2012, Debug, Release and x86 and x64. That gives 8 different .lib files which need to be compiled up with the proper VS version etc, so this is more manual right now than it could be...
With unmanaged stuff like this, it's unfortunately hard to get rid of. The .lib files are tightly connected to a particular VS version, much more than is the case with e.g. C# (which is tons more convenient in this aspect).
Does this answer your question? :)
If CefSharp isn't right for you, there's also the CefGlue project. I haven't used it myself but you can also give it a try if CefSharp doesn't fit the bill.
Best regards,
Per