I can't find an example of how to place a folder to binary files next to a project. To create a clear hierarchy. It used to be like this:
GlobalCEFApp.library := 'cef\libcef.dll';
GlobalCEFApp.FrameworkDirPath := 'cef\';
GlobalCEFApp.ResourcesDirPath := 'cef\';
GlobalCEFApp.LocalesDirPath := 'cef\locales\';
But now he says there is an error in this line
GlobalCEFApp.library := 'cef\libcef.dll';
Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
Storage folder
- salvadordf
- Posts: 4580
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: Storage folder
It's possible to move some of the files but CEF has some hardcoded dependencies between some of the files in the CEF binaries and you will have to keep them in the same directory.
It's a little bit outdated but this page explains most of the GlobalCEFApp properties :
https://www.briskbard.com/index.php?lang=en&pageid=cefapp
The GlobalCEFApp properties used to populate cef_settings_t are explained in the CEF source code comments :
https://bitbucket.org/chromiumembedded/cef/src/master/include/internal/cef_types.h
GlobalCEFApp.FrameworkDirPath :
GlobalCEFApp.ResourcesDirPath :
GlobalCEFApp.LocalesDirPath :
The README file inside the CEF binaries has more information about each file.
See the TCefApplicationCore.CheckCEFResources function in uCEFApplicationCore.pas for more details.
It's a little bit outdated but this page explains most of the GlobalCEFApp properties :
https://www.briskbard.com/index.php?lang=en&pageid=cefapp
The GlobalCEFApp properties used to populate cef_settings_t are explained in the CEF source code comments :
https://bitbucket.org/chromiumembedded/cef/src/master/include/internal/cef_types.h
GlobalCEFApp.FrameworkDirPath :
Code: Select all
///
// The path to the CEF framework directory on macOS. If this value is empty
// then the framework must exist at "Contents/Frameworks/Chromium Embedded
// Framework.framework" in the top-level app bundle. If this value is
// non-empty then it must be an absolute path. Also configurable using the
// "framework-dir-path" command-line switch.
///
GlobalCEFApp.ResourcesDirPath :
Code: Select all
///
// The fully qualified path for the resources directory. If this value is
// empty the *.pak files must be located in the module directory on
// Windows/Linux or the app bundle Resources directory on MacOS. If this
// value is non-empty then it must be an absolute path. Also configurable
// using the "resources-dir-path" command-line switch.
///
Code: Select all
///
// The fully qualified path for the locales directory. If this value is empty
// the locales directory must be located in the module directory. If this
// value is non-empty then it must be an absolute path. This value is ignored
// on MacOS where pack files are always loaded from the app bundle Resources
// directory. Also configurable using the "locales-dir-path" command-line
// switch.
///
See the TCefApplicationCore.CheckCEFResources function in uCEFApplicationCore.pas for more details.