Using libcef_static directly

[gusverdun]

Is there a way to compile the cefclient sample in a way that it does not use libcef.dll and instead links to cef and chrome libs statically?

The instructions on the wiki page (http://code.google.com/p/chromiumembedded/wiki/LinkingDifferentRunTimeLibraries) mention a simple change to depend on libcef_static rather than libcef_dll_wrapper.

However, that does not link:

cefclient_win.obj : error LNK2019: unresolved external symbol "public: __thiscall CefByteReadHandler::CefByteReadHandler(unsigned char const *,unsigned int,class CefRefPtr<class CefBase>)" (??0CefByteReadHandler@@QAE@PBEIV?$CefefPtr@VCefBase@@@@@Z) referenced in function "public: virtual enum cef_retval_t __thiscall ClientHandler::HandleBeforeResourceLoad(class CefRefPtr<class CefBrowser>,class CefRefPtr<class CefRequest>,class CefStringBase<struct CefStringTraitsUTF16> &,class CefRefPtr<class CefStreamReader> &,class CefStringBase<struct CefStringTraitsUTF16> &,int)" (?HandleBeforeResourceLoad@ClientHandler@@UAE?AW4cef_retval_t@@V?$CefRefPtr@VCefBrowser@@@@V?$CefRefPtr@VCefRequest@@@@AAV?$CefStringBase@UCefStringTraitsUTF16@@@@AAV?$CefRefPtr@VCefStreamReader@@@@2H@Z)

Any pointers on how to do this would be greatly appreciated.

Thanks,

Gus

[magreenblatt]

CefByteReadHandler is part of the libcef_dll_wrapper project. To use this and other classes defined in cef_wrapper.h you will need to include the source files from the libcef_dll/wrapper directory in your static project.

[gusverdun]

Thanks for the quick response.

Any advice on how we could even eliminate the cpp -> c wrapper layer?

Thanks,

Gus

[magreenblatt]

What are you trying to accomplish by not using CEF as a DLL? Linking the Chromium and WebKit libraries statically will very likely cause you more problems then it's worth.

[gusverdun]

My client will also be using chrome's base and net lib and potentially some of the other third party libs perhaps even skia.
By statically linking with libcef_static, I could also reduce the duplication in the statically linked C/CPP run-time between the two modules.
I am also, trying to reduce as much the extra memory allocations and the cpp -> c layer seemed like a good start.

-Gus

[magreenblatt]

My client will also be using chrome's base and net lib and potentially some of the other third party libs perhaps even skia.

OK, linking statically makes sense in that case. The C API layer, which is provided by the libcef and libcef_dll_wrapper targets, will not be included when you link against libcef_static directly.

Be aware that statically linking some Chromium sub-components in a closed-source product may violate licensing terms. See http://code.google.com/chromium/terms.html for more information.