Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create "chrome31" branch and an archive 31.2 release before updating to a newer CEF #172

Closed
GoogleCodeExporter opened this issue Aug 28, 2015 · 1 comment
Milestone

Comments

@GoogleCodeExporter
Copy link

Create the branch only after CEF 1 code path was removed (Issue 106). Make sure
there are no CEF 1 binaries left. Also make sure that there aren't any CEF 3
binary files. The var/ directory is 1.21 MB, maybe remove some files from there.

@cztomczak cztomczak added this to the Update to Chrome 47 milestone Jan 26, 2016
@cztomczak cztomczak changed the title Create "chrome31" branch before updating to a newer CEF branch Create "chrome31" branch and an archive 31.2 release before updating to a newer CEF Feb 15, 2016
@cztomczak
Copy link
Owner

Removing CEF 1 code path might break things, so leaving as is. CEF 1 binaries removed (Issue #103). An archive 31.2 release is ready: https://github.com/cztomczak/cefpython/releases/tag/v31.2 .

New branch "cefpython31" created. This branch still contains some useful CEF Python 1 code that wasn't yet ported to CEF Python 3, so keep it in archive, as it contains:

  • panda3d example
  • http authentication dialog default implentation on Windows; a php example http_authentication.php

@cztomczak cztomczak modified the milestones: v47, Chrome 50+ Feb 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants