[meta-freescale] 3.10.17-1.0.0_beta meta-fsl-bsp-release layer

[Alok Kumar]

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.

Thanks
Alok


On Mon, Jan 20, 2014 at 10:14 PM, Eric Nelson <
eric.nelson at 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
>>
>> 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/
>
> 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
>
> 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 -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
>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20140123/ef59a925/attachment-0001.html>