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

Update CEF to a more recent version #271

Closed
DarkDeepBlue opened this Issue Dec 13, 2015 · 8 comments

Comments

Projects
None yet
6 participants
@DarkDeepBlue
Copy link
Contributor

DarkDeepBlue commented Dec 13, 2015

CEF should be updated to a more recent version, for example branch 2526.

CEF should be updated anyway to provide a proper ABI for GCC 5.3. The changes to the API are not really heavy and the current code can be changed easily.

The problem ist that the current stable branch is still not compatible with GCC 5.3, so maybe we should compile the whole CEF library using GCC 5.3.

@bebehei

This comment has been minimized.

Copy link
Contributor

bebehei commented Dec 13, 2015

BTW: I'm currently working on my server to setup a complete Jenkins installation. If someone could contribute a script to compile libcef, this would be great.

@DarkDeepBlue

This comment has been minimized.

Copy link
Contributor Author

DarkDeepBlue commented Dec 13, 2015

Firstly, the compilation of libcef is pretty resource consuming. I’m not sure how powerful your server is, but that is something you have to keep in mind. Also, the compilation of libcef should happen for all platforms we are interested in.

Secondly, why exactly do you need a script? The thing one have to do is to get all the dependencies and compile the source. Now, I’m not familiar with all the details of that particular library, but the general question is what would be the benefit of some sort of script here.

@bebehei

This comment has been minimized.

Copy link
Contributor

bebehei commented Dec 13, 2015

There is enough power to build cef in a reasonable time.

If you've got a script, this would give me some hints, how you use the combination of cef and inexor. That's all. 😄 The does not have to be high quality. I just should get the gist.

@Fohlen

This comment has been minimized.

Copy link
Member

Fohlen commented Dec 13, 2015

There's an automatic build flow for libCEF provided by Google which can be found here
https://bitbucket.org/chromiumembedded/cef/wiki/BranchesAndBuilding.md#markdown-header-automated-method

@Fohlen

This comment has been minimized.

Copy link
Member

Fohlen commented Dec 13, 2015

Considering the branch to choose we should follow Chromiums release schedule, 2357 is the latest stable release branch AFAIK. Concerning the resources you need to think of an architecture that can share the working directory as well as the build cache since that's about 16 gigabyte and you really don't want to download that independantly for every container

@DarkDeepBlue

This comment has been minimized.

Copy link
Contributor Author

DarkDeepBlue commented Dec 16, 2015

On Archlinux Chromium actually uses branch 2526 since around 2015-12-02. Hence, I think that branch 2526 of CEF is also stable.

@bebehei

This comment has been minimized.

Copy link
Contributor

bebehei commented Jan 13, 2016

One month later: I had been able to create a libcef-git PKGBUILD. This is currently based on branch 2526. I'm testing the PKGBUILD right now. (in terms of dependencies. This takes time and requires rebuilding the full PKGBUILD for every change.) Details about a repo will follow, too.

If you want to testbuild inexor against the current libcefbranch, you can download my package. The package contains /usr/lib/libcef.so (which is obviously the library 😄 ) and /usr/share/libcef-full-list (which contains the full export built by ninja.). Yes, the package-function need some fixes, too!

@a-teammate a-teammate added feat:ui and removed cef labels Apr 26, 2016

@aschaeffer

This comment has been minimized.

Copy link
Member

aschaeffer commented Apr 27, 2016

Done in 669bc51 in branch karo+fohlen+hanack/fix_cef

@aschaeffer aschaeffer closed this Apr 27, 2016

@aschaeffer aschaeffer added this to the 0.9.0-alpha milestone Feb 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment