Matching Version Numbers with chromiumembedded

[bmukes]

For the life of me I cannot figure out the version number scheme that is used between CEFGlue and chromiumembedded
For example if I navigate to 'https://bitbucket.org/xilium/xilium.cefglue/commits/all' and look at commit 3caa551 I see where the version number was updated to 3.1384.1045 with the code define CEF_REVISION 1045

However when I browse the branches at http://code.google.com/p/chromiumembedd ... 2Fbranches
The highest number branch that I see is 1364 and I would guess that there would be a branch 1384. I am really confused.

The reason I ask is I am trying to figure out when the binaries at http://xilium.bitbucket.org/cefglue/ are updated with changes fixed in the chromiumembedded framework.

Thanks

[magreenblatt]

When building from trunk CEF's minor version number will be whatever value for "BUILD" exists in the chrome/VERSION file.

See http://code.google.com/p/chromiumembedd ... ail?id=325 for more information.

[fddima]

The reason I ask is I am trying to figure out when the binaries at http://xilium.bitbucket.org/cefglue/ are updated with changes fixed in the chromiumembedded framework.

CefGlue matched to CEF3 trunk versions and doesn't support release branches, at this moment.
Once we get stable CefGlue, i think we will support CEF feature branches. But just now i doesn't see any sense.

If you want switch to some other CEF version with CefGlue - you need get CefGlue sources, have already builded CEF (with full includes) - place includes in CefGlue.Interop.Gen/include and regenerate some interop code with gen-cef3.cmd. Cause structs and actual API (public) code not generated automatically, so then you need reflect all changes by hands. Some times it is very easy, some times it is not so easy, and it is are tricky.

Xilium CEF binaries i'm trying update fast as possible, but when have time for it. For example i'm already prepare 1093 build, but not publish it, and this build already outdated. So at next days i will build 1102.