magreenblatt wrote:Good blog post. A few comments:
1. Windows uses standard WinAPI HWND handles. There are no MFC dependencies.
2. You don't need to call get() when passing a CefRefPtr<> unless the type stored in the CefRefPtr<> changes (for example from MyClient to CefClient).
3. You can put the CEF header files in whatever directory you like (for example /path/to/cef/include) and use the compiler include path directive to point to the correct location (for example -I/path/to/cef).
4. The libcef_dll_wrapper.a static library should contain all of the object code (.o files). If it doesn't then there may be a bug in how we're creating the static library.
Thanks for your response! I'll be sure to get the post and code updated.
1. The Windows reference is probably due to my lack of experience with Windows development. It's good to know it doesn't require MFC.
2. Oh, ok. I didn't look at how CefRefPtr<> works internally, I'll get this updated.
3. This is what I'm doing now, I think. If you take a look at the git repo (
https://github.com/aphistic/cef3barebones) I have an include directory with my project's header files and then a cef3/ directory with an additional include/ directory with the CEF include files. The change I mentioned would allow me to put the CEF headers in my project's include/ directory (under something like include/cef/) so I can still keep those files separate, but only have one include/ directory. If the way it is currently is the standard way of including external libraries, I apologize. I spend most of my time in the .Net realm and don't work with C++ as much as I would like.
4. It could be the location I pulled the static library from (chromium/src/out/Release/obj.target/cef/libcef_dll_wrapper.a). This was the only place I could find the file after running a build (I did a manual build with: make BUILDTYPE=Release -j4 cefclient). I'm also using 1271 and not the latest version, so it could also be that.
I appreciate you spending the time to read my post! It's great to see all your posts on the forum and your dedication to the project.