Build fail

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.

Build fail

Postby sam007 » Thu Jul 14, 2016 11:22 am

I am trying to build CEF locally for a particular branch and I am using the following code,

Code: Select all
C:/Python27/python.exe D:/CEF/automate-git.py --download-dir=D:/CEF/CEFgrossa
g_build --branch=trunk --force-build --x64-build --verbose-build --url=https://xstarjedi@bitbucket.org/xstarjedi/cef-grossag-forked.git --no-cef-update --build-tests --no-release-build --no-distrib-archive --distrib-subdir=win32


After running the build for few hours I found it through this error. (Full log)

After going through some of the queries in CEF forum, I found that I need to
Code: Select all
set DEPOT_TOOLS_WIN_TOOLCHAIN=0
or at least have it in my environment variable. I could not find any reference to this in the automate build portion of BranchesAndBuilding.

Is there some other environment variable I should set before I restart my build? I am building CEF locally for the first time so want to make sure I have everything covered.

Also, while building since I encountered an error, can I simply start rebuilding from there or do I have to start from scratch (like pull in CEF again and run the build in a new folder?)
Last edited by sam007 on Thu Jul 14, 2016 12:00 pm, edited 2 times in total.
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Re: Build fail

Postby magreenblatt » Thu Jul 14, 2016 11:34 am

What CEF branch are you building? Are you using the most up-to-date version of automate-git.py from https://bitbucket.org/chromiumembedded/ ... ew-default?
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Build fail

Postby sam007 » Thu Jul 14, 2016 11:46 am

No, I am trying to build this branch so that I can make use of the changes in that branch. Do I need to make some changes so that I can get the build working?
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Re: Build fail

Postby sam007 » Thu Jul 14, 2016 11:56 am

magreenblatt wrote:What CEF branch are you building? Are you using the most up-to-date version of automate-git.py from https://bitbucket.org/chromiumembedded/ ... ew-default?


Sorry thought you were asking about the CEF branch being up to date. I checked my automate-git.py file with the link you gave and they are identical files.
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Re: Build fail

Postby magreenblatt » Thu Jul 14, 2016 12:01 pm

What CEF branch are you building? It looks like you are using Visual Studio 2013. Newer branches require VS2015. See https://bitbucket.org/chromiumembedded/ ... uilding.md for build requirements.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Build fail

Postby sam007 » Thu Jul 14, 2016 12:05 pm

magreenblatt wrote:What CEF branch are you building? It looks like you are using Visual Studio 2013. Newer branches require VS2015. See https://bitbucket.org/chromiumembedded/ ... uilding.md for build requirements.


I am using this branch. Will run the build with VS2015.
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Re: Build fail

Postby magreenblatt » Thu Jul 14, 2016 12:09 pm

sam007 wrote:
magreenblatt wrote:What CEF branch are you building? It looks like you are using Visual Studio 2013. Newer branches require VS2015. See https://bitbucket.org/chromiumembedded/ ... uilding.md for build requirements.


I am using this branch. Will run the build with VS2015.

If that is Chromium 1824 branch then it's highly unlikely you'll be able to build it. Currently supported branches include 2743 and 2785.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Build fail

Postby sam007 » Thu Jul 14, 2016 12:30 pm

I think the CEF branch version is 2526 or 2623. Even these cannot be used to build?

The branch name is "1824-testing". Where can I find the CEF branch version in the code? (Sorry still new to CEF and C++)
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Re: Build fail

Postby magreenblatt » Thu Jul 14, 2016 12:41 pm

Look at the CHROMIUM_BUILD_COMPATIBILITY.txt file. It appears to be an old version of Chromium master from February of this year. That would likely place it somewhere between 2623 and 2704. It should be possible to build code in that range, but you'd likely have better luck building a release branch instead of old versions of master.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Build fail

Postby sam007 » Thu Jul 14, 2016 12:50 pm

I actually need the changes made in that branch to display a Client Certificate List dialog for authentications like PKI (Public Key Infrastructure). I will be using the build binaries from that and add it to CefSharp.

magreenblatt wrote:CHROMIUM_BUILD_COMPATIBILITY.txt


I looked into it and it shows
Code: Select all
'chromium_checkout': '088f14a08fb102ca523424290965c04052eca325'


How do I connect it to what CEF branch version it is?
sam007
Techie
 
Posts: 46
Joined: Thu Feb 18, 2016 12:36 pm

Next

Return to Support Forum

Who is online

Users browsing this forum: No registered users and 40 guests