The CEF version number format was updated a few months ago and it's described here :
https://bitbucket.org/chromiumembedded/ ... ber-format
I just updated CEF4Delphi to the latest CEF version, 75.0.13. It uses the binaries built using the 3770 branch that includes the latest commit for that branch : 2c92fcd
If you run the MiniBrowser demo and visit chrome://version/ you will see this :
- CEF 75.0.13+g2c92fcd+chromium-75.0.3770.100
- Chromium 75.0.3770.100
The CEF version number has this format :
I hope this is enough to solve your problem. As I've mentioned before I've never built the binaries.After further discussion the proposal is to use:Where:
- "X.Y.Z+gHHHHHHH+chromium-A.B.C.D" for release branch builds.
- "X.0.0-master.N+gHHHHHHH+chromium-A.B.C.D" for master branch builds.
- "X" is the Chromium major version (e.g. 72).
- "Y" is an incremental number that starts at 0 when a release branch is created and changes only when the CEF C/C++ API changes (similar to how the CEF_API_HASH_UNIVERSAL value behaves in cef_version.h) (release branch only).
- "Z" is an incremental number that starts at 0 when a release branch is created and changes on each commit, with reset to 0 when "Y" changes (release branch only).
- "N" is an incremental number representing the number of commits (master branch only).
- "gHHHHHHH" is the 7-character abbreviation for the Git commit hash. This facilitates lookup of the relevant commit history in Git.
- "A.B.C.D" is the Chromium version (e.g. 72.0.3626.96).
There are some other forum users who have experience building the CEF binaries but if you still have problems building the binaries you can also ask for help in the official CEF forum :
http://magpcss.org/ceforum/