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

Adapt to packages being available in upstream Buildroot #9

Open
aperezdc opened this issue Feb 18, 2019 · 8 comments
Open

Adapt to packages being available in upstream Buildroot #9

aperezdc opened this issue Feb 18, 2019 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@aperezdc
Copy link
Member

Packages for some of the components are starting to appear in Buildroot's next branch (e.g. wpewebkit, libwpe) and they should be removed from this overlay.

Note that there is still value in having an overlay:

  • Providing packages which may not have made it yet to upstream Buildroot (example: wpebackend-rdk).
  • Providing ready to use configurations for popular boards.
@aperezdc aperezdc added the enhancement New feature or request label Feb 18, 2019
@aperezdc aperezdc self-assigned this Feb 18, 2019
@munezbn
Copy link
Contributor

munezbn commented May 24, 2019

Hi @aperezdc
What is the future of wpebackend-rdk , any plan when it will make it to buildroot ?

@aperezdc
Copy link
Member Author

@munezbn The goal is to move as many stable components as possible to Buildroot upstream. We have just managed to have WPE WebKit updated to 2.24.x (and compatible versions of libwpe, wpebackend-fdo, and cog). I still want to keep some things like wpebackend-rdk in this overlay because there are no official releases, as well as import using it for defconfigs and some miscellaneous tools.

@aperezdc
Copy link
Member Author

One thing more: I would really prefer that the RDK backend had releases in some way, which would simplify packaging and make it easier to track which versions are compatible with the different WPE WebKit and libwpe releases. That would also make it much more feasible to have a package included in Buildroot.

@munezbn
Copy link
Contributor

munezbn commented Jun 8, 2019

@aperezdc Agree with you. Even I was hoping that there will be some RDK backend release package which will make it easier to submit to buildrrot.

@harmon25
Copy link

harmon25 commented Apr 1, 2020

@aperezdc is there any reference on compatibility between the RDK backend and other wpe components?

I am playing around with an rpi3 buildroot leveraging the latest wpe components (wpewebkit 2.28.0, libwpe 1.6.0, cog 0.6.0) - and hoping to confirm that the master branch will be compatible.

Thanks for the help!

@aperezdc
Copy link
Member Author

aperezdc commented Apr 1, 2020

@harmon25 I haven't tried the RDK backend since WebKit 2.26.x, but as far as I can remember there has not been any change in 2.28.0 which would affect the RDK backend—the master branch should work.

It would definitely be nice if the maintainers of the RDK backend would put up a wiki page (or a README, at least) indicating which revisions are compatible with which WPE WebKit and libwpe versions. As a bonus, it would be even better if there was releases, or at least tags in the Git repository. I have filed WebPlatformForEmbedded/WPEBackend-rdk#35 but no reply so far.

@harmon25
Copy link

harmon25 commented Apr 2, 2020

Thanks for the info!
I just got everything working with latest, at least it is launching and navigating to a website...

Yea I noticed your efforts over there, it would be helpful for sure if there was some versioning information.

@CodeTrap
Copy link

CodeTrap commented Jun 7, 2021

It would be helpfull, if someone mentioned the buildroot version used on this one....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants