Updating chrome branch

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Updating chrome branch

Postby PeterO » Thu Aug 14, 2014 1:06 am

Hello everyone.

At the moment I'm trying to update my current chrome branch.
Current version is 33.0.1750.117.
I want to update to revision 33.0.1750.170.

First I need the chromium version equivalent:
https://omahaproxy.appspot.com/ gives 258314
http://src.chromium.org/svn/releases/33.0.1750.170/ gives 289471
http://src.chromium.org/viewvc/chrome/releases/ gives 258339

Then I execute: gclient sync --revision=src@<nr> using one of the numbers.
But the branch remains unchanged.
What am I doing wrong?

Regards,
Peter
PeterO
Techie
 
Posts: 16
Joined: Tue Dec 10, 2013 1:44 am

Re: Updating chrome branch

Postby Czarek » Thu Aug 14, 2014 1:28 am

To get Chromium revision for specific branch use this url:
Code: Select all
http://src.chromium.org/viewvc/chrome/branches/1750/src/chrome/VERSION
Maintainer of the CEF Python, PHP Desktop and CEF C API projects. My LinkedIn.
User avatar
Czarek
Virtuoso
 
Posts: 1927
Joined: Sun Nov 06, 2011 2:12 am

Re: Updating chrome branch

Postby magreenblatt » Thu Aug 14, 2014 2:42 am

See http://code.google.com/p/chromiumembedd ... ndBuilding for instructions on downloading/building release branches. Hint: You need to run 'gclient config' or edit the existing .gclient file.
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm

Re: Updating chrome branch

Postby PeterO » Thu Aug 14, 2014 5:52 am

But if I use 'gclient config' with the 170 revision and I do a 'glient sync' afterwards, it needs a clean 'src' folder, so that means a complete checkout!
Isn't it possible to update my current 1750 branch, revision 117 to revision 170 using: 'gclient sync --revision=src@<nr>'?
PeterO
Techie
 
Posts: 16
Joined: Tue Dec 10, 2013 1:44 am

Re: Updating chrome branch

Postby magreenblatt » Thu Aug 14, 2014 7:07 am

PeterO wrote:But if I use 'gclient config' with the 170 revision and I do a 'glient sync' afterwards, it needs a clean 'src' folder, so that means a complete checkout!
Isn't it possible to update my current 1750 branch, revision 117 to revision 170 using: 'gclient sync --revision=src@<nr>'?

The tooling doesn't really support that. You would need to edit the DEPS file and change the src revision. If other DEPS have changed then the build may fail.
magreenblatt
Site Admin
 
Posts: 12408
Joined: Fri May 29, 2009 6:57 pm


Return to Support Forum

Who is online

Users browsing this forum: No registered users and 75 guests