Upcoming Build Changes

[magreenblatt]

NOTE: This thread has been deprecated in favor of the cef-announce mailing list discussed here.

This topic will be used to announce upcoming build changes as they occur. For example:

• Changes in build infrastructure (download sources, automated build providers, etc).
• Changes in build tooling (required compiler versions, source repositories, utilities, etc).
• New CEF release branches.
• Other changes that may impact people building CEF/Chromium from source code or downloading CEF binaries.

Please see the CEF Wiki pages for a complete picture of CEF build and usage requirements.

You can subscribe to this topic by clicking the "Subscribe topic" link at the bottom of this page. If you have any questions about these announcements please ask in the CEF Discussion forum.

[magreenblatt]

As of March 11, 2016 Chromium requires VS2015 update 2 RC when building on Windows: https://groups.google.com/a/chromium.or ... 1gPacBCgAJ

This impacts CEF master revision 243a9c2 and newer. All Windows builders of CEF master should be updated to VS2015 update 2 RC before April 1, 2016 to avoid potential build breakage as Chromium removes VS2013 compatibility. Existing release branches (through 2623) will continue to require VS2013 update 4 as specified on the BranchesAndBuilding Wiki page.

This change does not impact users of the CEF binary distribution -- older Visual Studio versions will continue to be supported by the binary distribution.

[magreenblatt]

Chromium build requirements have changed as follows:

• As of April 4, 2016 Chromium-based applications must use 10.7+ as the deployment target on OS X. 10.6 is no longer supported as a deployment target. See https://crbug.com/592663#c14 for additional details.
• As of April 12, 2016 Chromium requires VS2015 Update 2 when building on Windows. See https://groups.google.com/a/chromium.or ... MA5sPxLwAJ additional details.

These changes impact CEF master revision e7ddc93 and newer.

[magreenblatt]

The CEF 2704 release branch tracking Chromium 51 is now available in source code form. See the BranchesAndBuilding Wiki page for build instructions. Binary distribution builds should be available from http://cefbuilds.com in the near future.

Starting with this release branch Windows XP, Windows Vista, and Mac OS X 10.6, 10.7, and 10.8 are no longer supported. See here for the original end-of-support announcement. Supplementary announcements are available here for Windows and here for OS X.

[magreenblatt]

I'm happy to announce the availability of a new Automated CEF Builder hosted by our friends over at Spotify: http://opensource.spotify.com/cefbuilds/index.html

This builder is based on code (Python + HTML/JS/CSS) that has been open sourced as part of the CEF project. The new AutomatedBuildSetup Wiki page provides a brief description of how this builder is set up and how you can now set up your own automated builder using the provided tools.

Unlike https://cefbuilds.com this new builder runs nightly builds of just the recommended branch. For example, since 2704 branch just reached the Chromium stable channel that branch is currently recommended. Older branch builds will still be discoverable using the filter capability (give it a try once more builds are listed). Depending on your zone is may take up to 24 hours for the index file updates to propagate -- so please be patient while waiting for the most recent builds to show up.

In addition to the index.html file linked above there is also an index.json file described here that can be parsed by tools for automatic discovery of downloads. We'll be publishing some new CMake macros and examples in the next few weeks that demonstrate this usage.

[magreenblatt]

The CEF 2743 release branch tracking Chromium 52 is now available in source code form. See the BranchesAndBuilding Wiki page for build instructions.

[magreenblatt]

Previously, the CEF project would track every other Chromium release branch and the two most recent CEF branches would be supported. Beginning today (June 6, 2016) the CEF release policy is changed to the following:

• A CEF branch will be created to track each Chromium release milesone (MXX) branch.
• Support for newer branches will begin when they enter the Chromium beta channel.
• Support for older branches will end when they exit the Chromium stable channel.

Additional notes:

• Chromium updates for CEF master branch will occur approximately once per month, and usually to the branch point for the next Chromium release. This means that CEF master branch will almost always be missing Chromium bug fixes that exist in the currently supported release branches.
• Always test with recent builds from a supported release branch before reporting new bugs.
• Please do not report new bugs against unsupported release branches. Any such reports will likely be closed as WontFix.
• The Spotify automated builder will provide CEF builds for the current Chromium stable channel. It will switch to the next Chromium branch when that branch is promoted to the stable channel.
• Updating CEF branches is currently a manual process. As a result there will likely be a delay between Chromium release announcements and the availability of associated CEF builds. Please be patient while waiting for new branches and/or builds to become available.
• See the Chromium release calendar for estimated Chromium release dates and versions.
• Subscribe to the chromium-dev mailing list for "MXX branch is here!" email announcements.

[magreenblatt]

The CEF 2785 release branch tracking Chromium 53 is now available in source code form. See the BranchesAndBuilding Wiki page for build instructions.

[magreenblatt]

The Chromium project is moving from GYP to GN as the build system of choice. CEF will require GN starting with the next release branch (after 2785). This change will be landing in the CEF master branch in the near future. What this means for you as a builder of CEF:

• Environment variables prefixed with GYP_* will no longer be honored. Use the GN_* equivalents instead (note that argument names will also have changed).
• GN does not support configuration via global system files (~/.gyp/include.gypi, etc). You must instead specify them via the GN_DEFINES environment variable.

See issue #1403 for additional details. Add yourself as a Watcher of that issue to be notified of changes.