On 8/15/17 6:05 AM, Raphael Kubo da Costa wrote: > Otavio Salvador <[email protected]> writes: > >>>> On Mon, Aug 14, 2017 at 12:22 PM, Jussi Kukkonen >>>> <[email protected]> wrote: >>>>> On a related note, this good work is currently a bit hidden in >>>>> meta-crosswalk -- is there a chance we could get this combined with >>>>> meta-browser (or whatever place makes sense)? I know next to nothing about >>>>> chromium packaging so CCing Raphael and the meta-browser maintainers for >>>>> comments. >> >> Indeed it does sound like the proper workaround for now. That said, >> I'd love to receive more help from meta-crosswalk people and avoid >> duplication of work in packaging Chromium so I am adding Raphael on Cc >> here so he can comment about how we can try to work together on this. > > The main reason why we haven't worked together yet is procrastination > from my side :-) > > My recipe's working fine and is up-to-date with Chromium's stable > releases, but I'd love to find a more permanent home for it and stop > duplicating the efforts, especially as I spend most of my time working > on Chromium itself, not its Yocto recipe or even Yocto in general. > > The main reason why I opted to start my recipe from scratch at the time > was simplicity: the meta-browser repository used the same recipe for > Chromium, CEF and Chromium with Ozone-Wayland, offered many different > options and shipped quite a few patches that made updates quite > difficult. My recipe is a lot less customizable, but OTOH that makes it > quite easy to move to new Chromium milestones. If we're able to find a > balance there, I definitely think we'd be able to get a lot more done > together.
what are main architectures targetted with crosswalk ? I think scope is important, since meta-browser supports, almost all oe-core supported architectures. including x86/arm/mips/ppc, any cross build patches are required in anycase, but architecture patches will be additional if you were only considering a subset of architectures. > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
