Page 1 of 1

Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 5:13 am
by zsmj01
Dear all:
I want to build a libcef.dll dynamic library on windows pc by cef1 1453 branch. And I know that cef1 has already retirement.

After I downloaded all files by automate.py, I executed the batch file cef_create_projects.bat, it prompted two errors I really can't resolve.

Two errors is :
Code: Select all
________ running 'E:\CEF\download\chromium\src\third_party\python26\python.exe tools/gyp_cef cef.gyp -I cef.gypi' in 'E:\CEF\download\chromium\src\cef'
Updating projects from gyp files...

Traceback (most recent call last):

  File "<string>", line 1, in <module>

  File "E:\CEF\download\chromium\src\third_party\python26\lib\multiprocessing\forking.py", line 341, in main

    prepare(preparation_data)

  File "E:\CEF\download\chromium\src\third_party\python26\lib\multiprocessing\forking.py", line 450, in prepare

    file, path_name, etc = imp.find_module(main_name, dirs)

ImportError: No module named gyp_cef


I has googled the key "prepare(preparation_data)" and found a similar page https://code.google.com/p/v8/issues/detail?id=2973#makechanges

The page said v8 need use revision 1685 of GYP. But the revision 1685 of GYP coundn't in the current GYP repository.

Thanks in advance.

Re: Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 5:40 am
by magreenblatt
What command line did you pass to automate.py?

Re: Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 5:50 am
by zsmj01
magreenblatt wrote:What command line did you pass to automate.py?


I run automate.py without any arguments.

Thank you very much!

Re: Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 5:51 am
by magreenblatt
zsmj01 wrote:I run automate.py without any arguments.

That won't work. See here.

Re: Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 6:00 am
by zsmj01
magreenblatt wrote:
zsmj01 wrote:I run automate.py without any arguments.

That won't work. See here.


I run automate.py with a command line not without any.

Command line:python /path/to/automate/automate.py --download-dir=/path/to/download

I found out this command line in file "automate.README.txt".And I modified the file automate.py. The new code is :cef_url = 'http://chromiumembedded.googlecode.com/svn/branches/1453/cef1.

new svn workflow: python /path/to/automate/automate.py --download-dir=/path/to/download --url=http://chromiumembedded.googlecode.com/svn/branches/1650/cef3 --ninja-build

My old command line is similar with the new svn workflow, just without --ninja-build.

Thank you.

Re: Whether CEF1 can be built now?

PostPosted: Mon Dec 15, 2014 11:34 pm
by zsmj01
magreenblatt wrote:
zsmj01 wrote:I run automate.py without any arguments.

That won't work. See here.


That svn workflow isn't used for cef1.The cef1 auto script automate.py isn't correct.The current trunk of cef not have cef1.

Could you give me more tips ?

Re: Whether CEF1 can be built now?

PostPosted: Tue Dec 16, 2014 4:19 am
by magreenblatt
CEF1 is no longer built or supported, so it's quite possible that the supporting infrastructure (Chromium SVN, etc) no longer works.

Re: Whether CEF1 can be built now?

PostPosted: Tue Dec 16, 2014 4:46 am
by zsmj01
magreenblatt wrote:CEF1 is no longer built or supported, so it's quite possible that the supporting infrastructure (Chromium SVN, etc) no longer works.


That's not a good news.

Your works are very great.

Thanks so much.

I admire you that you could understand my Chinglish.