On OS X you are required to create a separate executable and app bundle for sub-processes. On Windows and Linux the same executable can be used for the main process and sub-processes.Sub-processes will be created for renderers, plugins, GPU, etc. The main application process is called the “browser” process. The below list summarizes the items of primary importance for this tutorial: See below for a detailed description of the required application layout on each platform. See the README.txt file included in the binary distribution for details on which of these files are required and which can be safely left out. They are included in the Debug/Release or Resources directory of the binary distribution. The CEF dynamic library, support files and resources will be the same for every CEF-based application. Client executable (cefsimple in this example).Resources (html/js/css for built-in features, strings, etc).Support files (*.pak and *.bin binary blobs, etc).The CEF dynamic library (libcef.dll on Windows, libcef.so on Linux, “Chromium Embedded amework” on OS X).Load the local file “c:\example\example.html” … if (url.empty()) url = "file://c:/example/example.html" … Application ComponentsĪll CEF applications have the following primary components:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |