From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
Date: Thu, 23 Jan 2014 08:14:08 -0700 [thread overview]
Message-ID: <52E131C0.3080602@mlbassoc.com> (raw)
In-Reply-To: <CACoWYqXpSFtd_beDQh8gSHfUMpKdCbsCg1pHD0ZGmNyqupd8wA@mail.gmail.com>
On 2014-01-23 08:08, Alok Kumar wrote:
> Eric,
>
> After building chromium, when I tried to launch it
>
> find / -name "chrome*"
> /usr/bin/chrome
> /usr/bin/chrome/chrome_100_percent.pak
> /usr/bin/chrome/chrome
> /usr/bin/chrome/chrome.pak
>
> I get following error.
> /usr/bin/chrome/chrome
>
> (chrome:2068): Gtk-WARNING **: cannot open display:
>
> Any thoughts, what I am missing here.
Do you have X running?
If you tried to run this from outside the X desktop, you'll need to do something like
DISPLAY=:0.0 /usr/bin/chrome/chrome
> On Mon, Jan 20, 2014 at 10:14 PM, Eric Nelson <eric.nelson@boundarydevices.com <mailto:eric.nelson@boundarydevices.com>> wrote:
>
> Hi Alok,
>
>
> On 01/20/2014 09:44 AM, Alok Kumar wrote:
>
> Hi Eric,
>
> I am not sure if I understand it. my apology.
>
>
> No sweat. Over a year in and I'm still figuring things out...
>
>
> I am following this
> http://wiki.wandboard.org/__index.php/Getting_started___with_Yocto_on_Wandboard <http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard>
>
> and took stable dora branch.
>
>
> I'd start with Daiane's docs on i.MX Community:
> http://layers.openembedded.__org/layerindex/branch/master/__layer/meta-gnome/ <http://layers.openembedded.org/layerindex/branch/master/layer/meta-gnome/>
>
> And O.S.Systems that describes how to specifically build for
> Nitrogen6x:
> http://www.ossystems.com.br/__blog/2013/04/15/yocto-with-__boundary-devices-nitrogen6x-5-__steps-only.html
> <http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html>
>
> Make sure you use the "dora" branch instead of "dylan" though.
>
>
> Now if I want to try chromium" beta,
> a) should I got to development branch first and get everything from below.
>
> repo init -u
> https://github.com/Freescale/__fsl-community-bsp-platform <https://github.com/Freescale/fsl-community-bsp-platform> -b master
>
>
> Again, you should stick with "Dora" unless you need something
> specific in "master".
>
>
> b) apply chromium recipe on this build and build the image.
>
>
> After the repo sync, you'll need to pull in the meta-browser
> layer:
> ~/yocto/sources$ git clone git://github.com/OSSystems/__meta-browser.git <http://github.com/OSSystems/meta-browser.git>
>
> And you'll need to add meta-browser and meta-gnome to your
> conf/bblayers.conf file:
>
> BBLAYERS = " \
> ...
> ${BSPDIR}/sources/meta-__openembedded/meta-gnome \
> ${BSPDIR}/sources/meta-browser \
> ...
> "
>
> And finally, you'll need to pull it into your build.
> The easy way is to add this to your local.conf file:
>
> IMAGE_INSTALL += " \
> chromium \
> "
>
> I'm not sure why, but when I went through these steps,
> I got complaints about the license for libav and
> was prompted to add this to local.conf:
>
> LICENSE_FLAGS_WHITELIST = "commercial"
>
> I think there's something screwy with that, though.
> The recipes in poky/meta/recipes-multimedia/__libav/
> appear to have a combination of GPL and LGPL
> licenses.
>
>
> c) where should I test this on Sabrelite or nitorgen6x ?
>
>
> We recommend the use of "nitrogen6x" for the MACHINE type.
> The resulting image will run on either the SABRE Lite
> or Nitrogen6X boards.
>
> Regards,
>
>
> Eric
>
>
>
>
> --
> Regards
> Alok Kumar
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-01-23 15:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 16:08 3.10.17-1.0.0_beta meta-fsl-bsp-release layer Alok Kumar
2014-01-20 16:21 ` Eric Nelson
2014-01-20 16:44 ` Alok Kumar
2014-01-20 20:58 ` Alok Kumar
2014-01-21 3:14 ` Eric Nelson
2014-01-21 14:42 ` Diego
2014-01-21 15:22 ` Booting 3.5.7 kernel on imx6sabresd? randy.krakora
2014-01-21 15:39 ` Otavio Salvador
2014-01-21 16:16 ` randy.krakora
2014-01-21 16:21 ` Otavio Salvador
2014-01-21 20:11 ` Ra37740@freescale.comndy
2014-01-21 20:23 ` Otavio Salvador
2014-01-21 21:03 ` Daiane.Angolini
2014-01-22 15:06 ` randy.krakora
2014-01-22 15:10 ` Fabio Estevam
2014-01-22 17:47 ` randy.krakora
2014-01-22 17:52 ` Fabio Estevam
2014-01-21 19:25 ` 3.10.17-1.0.0_beta meta-fsl-bsp-release layer Eric Nelson
2014-01-22 12:41 ` Alok Kumar
2014-01-23 8:41 ` Diego
2014-01-23 11:08 ` Alok Kumar
2014-01-23 15:08 ` Alok Kumar
2014-01-23 15:14 ` Gary Thomas [this message]
[not found] ` <CACoWYqXYmKAQ3L_9HjLvEEwJNQ56G+9ENcgup7t44D25EpTTcA@mail.gmail.com>
2014-01-23 16:06 ` Gary Thomas
2014-01-23 16:49 ` Alok Kumar
2014-01-24 16:41 ` Alok Kumar
2014-01-24 16:55 ` Eric Nelson
2014-01-24 21:30 ` Otavio Salvador
2014-01-23 15:43 ` Eric Nelson
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 18:40 alokcherryhills
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=52E131C0.3080602@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
/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.