1CONTENTS 2-------- 3 4cmake Contains CMake configuration files shared by all targets. 5 6Debug Contains libcef.dll, libcef.lib and other components required to 7 build and run the debug version of CEF-based applications. By 8 default these files should be placed in the same directory as the 9 executable and will be copied there as part of the build process. 10 11include Contains all required CEF header files. 12 13libcef_dll Contains the source code for the libcef_dll_wrapper static library 14 that all applications using the CEF C++ API must link against. 15 16Release Contains libcef.dll, libcef.lib and other components required to 17 build and run the release version of CEF-based applications. By 18 default these files should be placed in the same directory as the 19 executable and will be copied there as part of the build process. 20 21Resources Contains resources required by libcef.dll. By default these files 22 should be placed in the same directory as libcef.dll and will be 23 copied there as part of the build process. 24 25tests/ Directory of tests that demonstrate CEF usage. 26 27 cefclient Contains the cefclient sample application configured to build 28 using the files in this distribution. This application demonstrates 29 a wide range of CEF functionalities. 30 31 cefsimple Contains the cefsimple sample application configured to build 32 using the files in this distribution. This application demonstrates 33 the minimal functionality required to create a browser window. 34 35 ceftests Contains unit tests that exercise the CEF APIs. 36 37 gtest Contains the Google C++ Testing Framework used by the ceftests 38 target. 39 40 shared Contains source code shared by the cefclient and ceftests targets. 41 42 43USAGE 44----- 45 46Building using CMake: 47 CMake can be used to generate project files in many different formats. See 48 usage instructions at the top of the CMakeLists.txt file. 49 50Please visit the CEF Website for additional usage information. 51 52https://bitbucket.org/chromiumembedded/cef/ 53