Api hashes and frozen Api

[wborgsm]

Hi,

I noticed that there is an API change between cef_binary_3.2357.1274.g7b49af6_windows32 and cef_binary_3.2357.1280.geba024d_windows32. First is for CHROME_VERSION_PATCH 45 and second is for CHROME_VERSION_PATCH 81. This is also reflected by the different API hashes in cef_version.h.

Further I noticed that cef_binary_3.2357.1276.gd4b589c_windows64 (CHROME_VERSION_PATCH 81) is still API-compatible with cef_binary_3.2357.1274.g7b49af6_windows64 (CHROME_VERSION_PATCH 45).

This means I now have different APIs for CEF 32-bit and 64-bit targeting Chromium 43.0.2357.81. Is this intentional?

And does the following quote [1] still hold: "Within a release branch the CEF API is "frozen" and generally only security/bug fixes are applied"? Or should I expect API changes between different CHROME_VERSION_PATCH numbers within the same release branch as well?

[1] https://bitbucket.org/chromiumembedded/ ... e-branches

[magreenblatt]

Hi,

I noticed that there is an API change between cef_binary_3.2357.1274.g7b49af6_windows32 and cef_binary_3.2357.1280.geba024d_windows32. First is for CHROME_VERSION_PATCH 45 and second is for CHROME_VERSION_PATCH 81. This is also reflected by the different API hashes in cef_version.h.

Further I noticed that cef_binary_3.2357.1276.gd4b589c_windows64 (CHROME_VERSION_PATCH 81) is still API-compatible with cef_binary_3.2357.1274.g7b49af6_windows64 (CHROME_VERSION_PATCH 45).

This means I now have different APIs for CEF 32-bit and 64-bit targeting Chromium 43.0.2357.81. Is this intentional?

You're comparing 1274..1280 in 32-bit to 1274..1276 in 64-bit. You can use the same build of 32-bit and 64-bit (e.g. 1274) to avoid the problem.

And does the following quote [1] still hold: "Within a release branch the CEF API is "frozen" and generally only security/bug fixes are applied"? Or should I expect API changes between different CHROME_VERSION_PATCH numbers within the same release branch as well?

The quote still holds. There will occasionally be API changes in current release branches.

[wborgsm]

Hello, and welcome back from holidays (I guess?)

You're comparing 1274..1280 in 32-bit to 1274..1276 in 64-bit. You can use the same build of 32-bit and 64-bit (e.g. 1274) to avoid the problem.

The problem is, there was no 64-bit binary for 3.2357.1280 and no 32-bit binary for 3.2357.1276 at cefbuilds.com - so for Chromium 43.0.2357.81 I downloaded two different builds. I was not aware that two builds within the same release branch could have different APIs, because I misunderstood the quoted statement, or better, I lazily disregarded the word "generally" and thought the API was strictly frozen. I'll have to fix that in my project.

Thanks.