All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jacobo Aragunde Pérez" <jaragunde@igalia.com>
To: openembedded-devel@lists.openembedded.org,
	Trevor Woerner <twoerner@gmail.com>
Subject: Re: [meta-browser][PATCH] chromium: 52.0.2743.76 -> 54.0.2810.2
Date: Fri, 7 Apr 2017 20:08:30 +0200	[thread overview]
Message-ID: <620eadc5-9119-633e-f937-1f906fea1408@igalia.com> (raw)
In-Reply-To: <CAHUNapR=5Tj+jAF5_hMgZ1MMSaEiGbNRrj36YL12zcETqhzBYA@mail.gmail.com>

Hi Trevor,

On 06/04/17 22:37, Trevor Woerner wrote:
> ...
> Currently I'm trying to figure out how to move past this version.
> After 53.0.2810.2 the current method OE uses to build chromium starts
> to fail because (as is my understanding) it was around this point that
> the chromium build switched from gyp+ninja (what we're using in OE) to
> gn+ninja (ninja is like "make" and gyp/gn are like the autotools)
> Therefore the gyp support starts to break down due to lack of upstream
> maintainership. I'm starting to be able to do successful chromium
> builds from tarballs on the cmdline (outside of OE) up to
> 57.0.2987.133 but I need to figure out how to translate that into a
> recipe.
> 

Some colleagues here have modified the recipe to build Chromium up to
version 57 using the new GN build system, targeting R-Car Gen.3 boards.
Unfortunately, the solution would still need a lot of cleanup before
being able to submit it.

Still, if you want to take a look and use it as an example, even reuse
parts of it in your own patch, feel free to do it.

Layer is here: https://github.com/Igalia/meta-browser

Best,
-- 
Jacobo Aragunde
Software Engineer at Igalia


      parent reply	other threads:[~2017-04-07 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 18:38 [meta-browser][PATCH] chromium: 52.0.2743.76 -> 54.0.2810.2 Trevor Woerner
2017-04-06  7:31 ` Martin Jansa
2017-04-06 20:37   ` Trevor Woerner
2017-04-07  8:08     ` Fathi Boudra
2017-04-07 18:56       ` Andrey Konovalov
2017-04-07 18:08     ` Jacobo Aragunde Pérez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=620eadc5-9119-633e-f937-1f906fea1408@igalia.com \
    --to=jaragunde@igalia.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.