From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eric.nelson@boundarydevices.com>
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com
	[209.85.220.51])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id BD616E00B67
	for <meta-freescale@yoctoproject.org>;
	Fri, 21 Mar 2014 07:17:43 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so2445094pab.24
	for <meta-freescale@yoctoproject.org>;
	Fri, 21 Mar 2014 07:17:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=XYk77sWlxXwcCmeRPZfi0weYjs8H6qf+IZ8JZm381eg=;
	b=HwWENrvYw6m6VEzI9XTCHSEFoSO3VH6uT3e7Kt0HG5r6hwLcJFo5gbwDvTJVhRKX9m
	KN0SxXJtTOOF5iWi7iZ4hDUanc5QDHkFJLtZFq/LuDeNtRfjjuAI5PUjUSxrbhTS0ho7
	bGu513d7R8SMJLKUt3nQP/I4iQRDKhwDkqijECHkBJ+9ZNrMdwHJqRQ8opo4/1G3aMhy
	/mg4NsusWLARnbZ8N43DmSfI0HpDEh+u7r46nukl1rC2Y5enAk3DELAOeVKASYhUB5vm
	r2wqjoQhXYrfAnN8Flz7JPIssfMnje5FMGteT/8jJwk+UcHLCzhR6KEtcQ3a0qx5kB6F
	l77w==
X-Gm-Message-State: ALoCoQn9UPO9sgnTQ+nCQkNfR4lIclLiaGW6Q8IbBn649tY7yMPPwEwCIJI6lTv5qWPPdXxzJdwt
X-Received: by 10.68.163.3 with SMTP id ye3mr54070651pbb.78.1395411463234;
	Fri, 21 Mar 2014 07:17:43 -0700 (PDT)
Received: from [192.168.1.8] (ip98-167-230-131.ph.ph.cox.net. [98.167.230.131])
	by mx.google.com with ESMTPSA id
	pe3sm10185363pbc.23.2014.03.21.07.17.40 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 21 Mar 2014 07:17:41 -0700 (PDT)
Message-ID: <532C4A01.8040708@boundarydevices.com>
Date: Fri, 21 Mar 2014 07:17:37 -0700
From: Eric Nelson <eric.nelson@boundarydevices.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Diego <diego.ml@zoho.com>, meta-freescale@yoctoproject.org
References: <3028891.a86zsWf6Zv@localhost.localdomain>
In-Reply-To: <3028891.a86zsWf6Zv@localhost.localdomain>
Subject: Re: Chromium acceleration
X-BeenThere: meta-freescale@yoctoproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Usage and development list for the meta-fsl-* layers
	<meta-freescale.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/meta-freescale>
List-Post: <mailto:meta-freescale@yoctoproject.org>
List-Help: <mailto:meta-freescale-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Mar 2014 14:17:45 -0000
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Diego,

On 03/21/2014 04:49 AM, Diego wrote:
> Otavio Salvador wrote:
>> Eric Nelson wrote:
>>> A simplistic test shows that it's really straightforward to
>>> add both Chromium and Firefox into fsl-image-gui by pulling
>>> in meta-browser.
>>
>> The biggest problem adding more stuff is maintenance. This increases
>> build time and tests needed for a good coverage.
>>
>> What people think?
>
> Hi Otavio and Eric,
>
> I think we can sum up your discussion in two points:
> - web applications and in general browser usage is really important nowadays
> in general, and it is taking its share of interest also in the embedded world;
> - firefox and chromium require quite a lot of resources both in terms of
> maintenance and in terms of build time and computation.
>
> I can confirm both points, as we have a couple of projects using Chromium. So
> on one hand it is something important to support and test regularly (and that
> would help finding build breakages), on the other hand build takes a lot time,
> and an overwhelming amount of RAM. I used to build images with Firefox and
> Chromium 29 with 6 bitbake build threads and it worked on a 4GB of RAM and 2GB
> swap, but now with Chromium 35 I had to pump up the VM to 12GB of RAM (8GB
> still killed the final ld linking process, which is the real "RAM eater").
>
> So while testing browsers would be nice, I think the best option would be to
> test it somehow separately from the fsl-image-gui. Do you think defining an
> image in meta-browser would make sense?
>

I wasn't suggesting that Chromium or Firefox be included in
fsl-image-gui. Only that meta-browser (and I think meta-gnome as a
dependency) be included in the default manifest.

This will prevent the need to "git clone" the repositories separately,
and allow inclusion through local.conf.

Regards,


Eric