From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Chromium
Date: Mon, 23 Apr 2018 21:25:05 +0200 [thread overview]
Message-ID: <20180423212505.68654293@windsurf> (raw)
In-Reply-To: <5B0BF4C3-9DC5-4199-BB4E-2B303C3EF2C8@gamecodehq.com>
Hello,
On Mon, 23 Apr 2018 13:15:36 +0200, Micha? Kalbarczyk wrote:
> Is there any chance to build chromium in build root environment?
> Found few old makefiles, but nothing actually works. Is this
> possible?
Yes, I believe it is possible, I don't see why it wouldn't be. Now,
Chromium is clearly not the easiest software to build, and therefore to
package in Buildroot.
So doable: yes, easy: definitely no.
In any case, we're interested in having patches submitted to Buildroot
to add such a package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-23 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 11:15 [Buildroot] Chromium Michał Kalbarczyk
2018-04-23 19:25 ` Thomas Petazzoni [this message]
2018-04-24 12:01 ` Michał Kalbarczyk
2018-04-25 1:51 ` Joseph Kogut
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=20180423212505.68654293@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox