* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
@ 2014-01-22 18:40 alokcherryhills
0 siblings, 0 replies; 19+ messages in thread
From: alokcherryhills @ 2014-01-22 18:40 UTC (permalink / raw)
To: Alok Kumar, Eric Nelson; +Cc: meta-freescale@yoctoproject.org, Diego
[-- Attachment #1: Type: text/plain, Size: 5463 bytes --]
Could someone please offer advice on this chrome building issues.
Thanks
Alok
Sent from my Windows Phone
------------------------------
From: Alok Kumar <alokkat@gmail.com>
Sent: 1/22/2014 7:41 AM
To: Eric Nelson <eric.nelson@boundarydevices.com>
Cc: Diego <diego.ml@zoho.com>; meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
I ran into following errors while building chromium for nitrogen6X, could
someone advise if something not compatible in my conf layer (below)
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbwindow.cpp:423:51:
warning: narrowing conversion of 'XEMBED_VERSION' from 'unsigned int' to
'long int' inside { } [-Wnarrowing]
long data[] = { XEMBED_VERSION, XEMBED_MAPPED };
^
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:
In constructor 'QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool,
const char*)':
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:275:50:
error: cannot convert 'Display* {aka _XDisplay*}' to 'EGLNativeDisplayType
{aka _FBDisplay*}' for argument '1' to 'void*
eglGetDisplay(EGLNativeDisplayType)'
EGLDisplay eglDisplay = eglGetDisplay(dpy);
^
make[5]: *** [.obj/release-shared/qxcbconnection.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[5]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms/xcb'
make[4]: *** [sub-xcb-plugin-pro-make_first-ordered] Error 2
make[4]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms/xcb'
make[3]: *** [sub-xcb-make_first] Error 2
make[3]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms'
make[2]: *** [sub-platforms-make_first] Error 2
make[2]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins'
make[1]: *** [sub-plugins-make_first] Error 2
make[1]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src'
make: *** [sub-src-make_first] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
*My conf/bblayer.conf is as below:*
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) +
'/../..')}"
BBFILES ?= ""
BBLAYERS = " \
${BSPDIR}/sources/poky/meta \
${BSPDIR}/sources/poky/meta-yocto \
\
${BSPDIR}/sources/meta-openembedded/meta-oe \
${BSPDIR}/sources/meta-openembedded/meta-gnome \
${BSPDIR}/sources/meta-openembedded/meta-browser \
\
${BSPDIR}/sources/meta-fsl-arm \
${BSPDIR}/sources/meta-fsl-arm-extra \
${BSPDIR}/sources/meta-fsl-demos \
${BSPDIR}/sources/meta-qt5 \
"
*And conf/local.conf*
MACHINE ??= 'nitrogen6x'
DISTRO ?= 'poky'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks ssh-server-openssh"
IMAGE_INSTALL_append = " eglibc-staticdev strace gcc g++ binutils libgcc
libgcc-dev libstdc++ libstdc++-dev libstdc++-staticdev tslib-conf
tslib-tests tslib-calibrate openssh-sftp-server alsa-lib alsa-tools
alsa-state alsa-utils-alsaconf tslib evtest dbus nano git qtbase gstreamer
cairo pango fontconfig freetype pulseaudio qtbase qtbase-fonts
qtbase-plugins qtbase-examples chromium"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
LICENSE_FLAGS_WHITELIST = "commercial"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K"
CONF_VERSION = "1"
BB_NUMBER_THREADS = '8'
PARALLEL_MAKE = '-j 8'
DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = ""
Thanks
Alok
On Tue, Jan 21, 2014 at 2:25 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:
> On 01/21/2014 07:42 AM, Diego wrote:
>
>> Eric Nelson wrote:
>>
>>> 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.
>>>
>>
>> Eric, I'd bet the:
>> LICENSE_FLAGS = "commercial"
>> in the libav recipe is because of the patents that cover several of the
>> included codecs (gsm, x264, mp3lame, etc).
>>
>> Thanks Diego,
>
> There seem to be lots of disclaimers about this library:
> http://libav.org/legal.html
>
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
Regards
Alok Kumar
[-- Attachment #2: Type: text/html, Size: 8913 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread* 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
@ 2014-01-20 16:08 Alok Kumar
2014-01-20 16:21 ` Eric Nelson
0 siblings, 1 reply; 19+ messages in thread
From: Alok Kumar @ 2014-01-20 16:08 UTC (permalink / raw)
To: meta-freescale
Hi,
I am interested in trying out 3.10.17-1.0.0_beta build, how could I
built it or try out the binaries.
I am looking for chromium browser to try on imx6 nitrogen6x.
Please advise.
--
Regards
Alok Kumar
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-20 16:08 Alok Kumar
@ 2014-01-20 16:21 ` Eric Nelson
2014-01-20 16:44 ` Alok Kumar
0 siblings, 1 reply; 19+ messages in thread
From: Eric Nelson @ 2014-01-20 16:21 UTC (permalink / raw)
To: Alok Kumar, meta-freescale
Hi Alok,
These are really two separate questions:
On 01/20/2014 09:08 AM, Alok Kumar wrote:
> Hi,
>
> I am interested in trying out 3.10.17-1.0.0_beta build, how could I
> built it or try out the binaries.
>
Please hold tight for patches to add 3.10.17-1.0.0_beta on
SABRE Lite/Nitrogen6x.
> I am looking for chromium browser to try on imx6 nitrogen6x.
>
You'll want to include the "meta-browser" layer:
https://github.com/OSSystems/meta-browser
And add the chromium recipe in your build.
Regards,
Eric
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
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
0 siblings, 2 replies; 19+ messages in thread
From: Alok Kumar @ 2014-01-20 16:44 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale
Hi Eric,
I am not sure if I understand it. my apology.
I am following this
http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard
and took stable dora branch.
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
b) apply chromium recipe on this build and build the image.
c) where should I test this on Sabrelite or nitorgen6x ?
Please advise.
Thanks
Alok
On Mon, Jan 20, 2014 at 11:21 AM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> Hi Alok,
>
> These are really two separate questions:
>
>
> On 01/20/2014 09:08 AM, Alok Kumar wrote:
>>
>> Hi,
>>
>> I am interested in trying out 3.10.17-1.0.0_beta build, how could I
>> built it or try out the binaries.
>>
> Please hold tight for patches to add 3.10.17-1.0.0_beta on
> SABRE Lite/Nitrogen6x.
>
>
>> I am looking for chromium browser to try on imx6 nitrogen6x.
>>
> You'll want to include the "meta-browser" layer:
> https://github.com/OSSystems/meta-browser
>
> And add the chromium recipe in your build.
>
> Regards,
>
>
> Eric
>
--
Regards
Alok Kumar
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-20 16:44 ` Alok Kumar
@ 2014-01-20 20:58 ` Alok Kumar
2014-01-21 3:14 ` Eric Nelson
1 sibling, 0 replies; 19+ messages in thread
From: Alok Kumar @ 2014-01-20 20:58 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale
I am running into error for libgnome-keyring.
NERROR: Nothing RPROVIDES 'libgnome-keyring' (but
/home/user/yocto/sources/poky/meta/recipes-core/images/core-image-base.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'libgnome-keyring' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libgnome-keyring']
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base',
'libgnome-keyring']
Any advise how to fix this error to build chromium ?
Thanks
Alok
On Mon, Jan 20, 2014 at 11:44 AM, Alok Kumar <alokkat@gmail.com> wrote:
> Hi Eric,
>
> I am not sure if I understand it. my apology.
>
> I am following this
> http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard
>
> and took stable dora branch.
>
> 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
>
> b) apply chromium recipe on this build and build the image.
> c) where should I test this on Sabrelite or nitorgen6x ?
>
> Please advise.
>
> Thanks
> Alok
>
> On Mon, Jan 20, 2014 at 11:21 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi Alok,
>>
>> These are really two separate questions:
>>
>>
>> On 01/20/2014 09:08 AM, Alok Kumar wrote:
>>>
>>> Hi,
>>>
>>> I am interested in trying out 3.10.17-1.0.0_beta build, how could I
>>> built it or try out the binaries.
>>>
>> Please hold tight for patches to add 3.10.17-1.0.0_beta on
>> SABRE Lite/Nitrogen6x.
>>
>>
>>> I am looking for chromium browser to try on imx6 nitrogen6x.
>>>
>> You'll want to include the "meta-browser" layer:
>> https://github.com/OSSystems/meta-browser
>>
>> And add the chromium recipe in your build.
>>
>> Regards,
>>
>>
>> Eric
>>
>
>
>
> --
> Regards
> Alok Kumar
--
Regards
Alok Kumar
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
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-23 15:08 ` Alok Kumar
1 sibling, 2 replies; 19+ messages in thread
From: Eric Nelson @ 2014-01-21 3:14 UTC (permalink / raw)
To: Alok Kumar; +Cc: meta-freescale
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
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-21 3:14 ` Eric Nelson
@ 2014-01-21 14:42 ` Diego
2014-01-21 19:25 ` Eric Nelson
2014-01-23 15:08 ` Alok Kumar
1 sibling, 1 reply; 19+ messages in thread
From: Diego @ 2014-01-21 14:42 UTC (permalink / raw)
To: meta-freescale
Eric Nelson wrote:
> 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.
Eric, I'd bet the:
LICENSE_FLAGS = "commercial"
in the libav recipe is because of the patents that cover several of the
included codecs (gsm, x264, mp3lame, etc).
Bests,
Diego
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-21 14:42 ` Diego
@ 2014-01-21 19:25 ` Eric Nelson
2014-01-22 12:41 ` Alok Kumar
0 siblings, 1 reply; 19+ messages in thread
From: Eric Nelson @ 2014-01-21 19:25 UTC (permalink / raw)
To: Diego, meta-freescale
On 01/21/2014 07:42 AM, Diego wrote:
> Eric Nelson wrote:
>> 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.
>
> Eric, I'd bet the:
> LICENSE_FLAGS = "commercial"
> in the libav recipe is because of the patents that cover several of the
> included codecs (gsm, x264, mp3lame, etc).
>
Thanks Diego,
There seem to be lots of disclaimers about this library:
http://libav.org/legal.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-21 19:25 ` Eric Nelson
@ 2014-01-22 12:41 ` Alok Kumar
2014-01-23 8:41 ` Diego
0 siblings, 1 reply; 19+ messages in thread
From: Alok Kumar @ 2014-01-22 12:41 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale, Diego
[-- Attachment #1: Type: text/plain, Size: 5060 bytes --]
I ran into following errors while building chromium for nitrogen6X, could
someone advise if something not compatible in my conf layer (below)
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbwindow.cpp:423:51:
warning: narrowing conversion of 'XEMBED_VERSION' from 'unsigned int' to
'long int' inside { } [-Wnarrowing]
long data[] = { XEMBED_VERSION, XEMBED_MAPPED };
^
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:
In constructor 'QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool,
const char*)':
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:275:50:
error: cannot convert 'Display* {aka _XDisplay*}' to 'EGLNativeDisplayType
{aka _FBDisplay*}' for argument '1' to 'void*
eglGetDisplay(EGLNativeDisplayType)'
EGLDisplay eglDisplay = eglGetDisplay(dpy);
^
make[5]: *** [.obj/release-shared/qxcbconnection.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[5]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms/xcb'
make[4]: *** [sub-xcb-plugin-pro-make_first-ordered] Error 2
make[4]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms/xcb'
make[3]: *** [sub-xcb-make_first] Error 2
make[3]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins/platforms'
make[2]: *** [sub-platforms-make_first] Error 2
make[2]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src/plugins'
make[1]: *** [sub-plugins-make_first] Error 2
make[1]: Leaving directory
`/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/qtbase/5.1.1-r0/build/src'
make: *** [sub-src-make_first] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
*My conf/bblayer.conf is as below:*
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) +
'/../..')}"
BBFILES ?= ""
BBLAYERS = " \
${BSPDIR}/sources/poky/meta \
${BSPDIR}/sources/poky/meta-yocto \
\
${BSPDIR}/sources/meta-openembedded/meta-oe \
${BSPDIR}/sources/meta-openembedded/meta-gnome \
${BSPDIR}/sources/meta-openembedded/meta-browser \
\
${BSPDIR}/sources/meta-fsl-arm \
${BSPDIR}/sources/meta-fsl-arm-extra \
${BSPDIR}/sources/meta-fsl-demos \
${BSPDIR}/sources/meta-qt5 \
"
*And conf/local.conf*
MACHINE ??= 'nitrogen6x'
DISTRO ?= 'poky'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks ssh-server-openssh"
IMAGE_INSTALL_append = " eglibc-staticdev strace gcc g++ binutils libgcc
libgcc-dev libstdc++ libstdc++-dev libstdc++-staticdev tslib-conf
tslib-tests tslib-calibrate openssh-sftp-server alsa-lib alsa-tools
alsa-state alsa-utils-alsaconf tslib evtest dbus nano git qtbase gstreamer
cairo pango fontconfig freetype pulseaudio qtbase qtbase-fonts
qtbase-plugins qtbase-examples chromium"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
LICENSE_FLAGS_WHITELIST = "commercial"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K"
CONF_VERSION = "1"
BB_NUMBER_THREADS = '8'
PARALLEL_MAKE = '-j 8'
DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = ""
Thanks
Alok
On Tue, Jan 21, 2014 at 2:25 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:
> On 01/21/2014 07:42 AM, Diego wrote:
>
>> Eric Nelson wrote:
>>
>>> 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.
>>>
>>
>> Eric, I'd bet the:
>> LICENSE_FLAGS = "commercial"
>> in the libav recipe is because of the patents that cover several of the
>> included codecs (gsm, x264, mp3lame, etc).
>>
>> Thanks Diego,
>
> There seem to be lots of disclaimers about this library:
> http://libav.org/legal.html
>
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
Regards
Alok Kumar
[-- Attachment #2: Type: text/html, Size: 7393 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-22 12:41 ` Alok Kumar
@ 2014-01-23 8:41 ` Diego
2014-01-23 11:08 ` Alok Kumar
0 siblings, 1 reply; 19+ messages in thread
From: Diego @ 2014-01-23 8:41 UTC (permalink / raw)
To: meta-freescale
In data mercoledì 22 gennaio 2014 07:41:03, Alok Kumar ha scritto:
> I ran into following errors while building chromium for nitrogen6X, could
> someone advise if something not compatible in my conf layer (below)
>
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbwin
> dow.cpp:423:51: warning: narrowing conversion of 'XEMBED_VERSION' from
> 'unsigned int' to 'long int' inside { } [-Wnarrowing]
> long data[] = { XEMBED_VERSION, XEMBED_MAPPED };
> ^
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> nection.cpp: In constructor
> 'QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, const char*)':
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> nection.cpp:275:50: error: cannot convert 'Display* {aka _XDisplay*}' to
> 'EGLNativeDisplayType {aka _FBDisplay*}' for argument '1' to 'void*
> eglGetDisplay(EGLNativeDisplayType)'
> EGLDisplay eglDisplay = eglGetDisplay(dpy);
> ^
Hi Alok,
please take a look closely to the error log, because I think you haven't.
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/qtbase/5.1.1-r0/qtbase-opensource-
src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:275:50:
error: cannot convert 'Display* {aka _XDisplay*}' to 'EGLNativeDisplayType
Can be easily seen is a qtbase 5.1.1 error, not a Chromium error. qtbase is
not required for Chromium.
Please remove qt related things from your IMAGE_INSTALL_append and try again.
Bests,
Diego
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-23 8:41 ` Diego
@ 2014-01-23 11:08 ` Alok Kumar
0 siblings, 0 replies; 19+ messages in thread
From: Alok Kumar @ 2014-01-23 11:08 UTC (permalink / raw)
To: Diego; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2731 bytes --]
Hi Diego,
Thanks for reply. Appreciate your feedback. I have a question, I would
like to use Qt WebEngine as mentioned in following blog.
http://blog.qt.digia.com/blog/2013/09/12/introducing-the-qt-webengine/
I thought of having some programming interface with chromium using QT
WebEngine which in introduced in QT 5.2.
Which package of QT in bblayer.conf and local.conf, I should be including
to accomplish this?
Thanks
Alok
On Thu, Jan 23, 2014 at 3:41 AM, Diego <diego.ml@zoho.com> wrote:
> In data mercoledì 22 gennaio 2014 07:41:03, Alok Kumar ha scritto:
> > I ran into following errors while building chromium for nitrogen6X, could
> > someone advise if something not compatible in my conf layer (below)
> >
> >
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> >
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbwin
> > dow.cpp:423:51: warning: narrowing conversion of 'XEMBED_VERSION' from
> > 'unsigned int' to 'long int' inside { } [-Wnarrowing]
> > long data[] = { XEMBED_VERSION, XEMBED_MAPPED };
> > ^
> >
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> >
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> > nection.cpp: In constructor
> > 'QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, const
> char*)':
> >
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> >
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> > nection.cpp:275:50: error: cannot convert 'Display* {aka _XDisplay*}' to
> > 'EGLNativeDisplayType {aka _FBDisplay*}' for argument '1' to 'void*
> > eglGetDisplay(EGLNativeDisplayType)'
> > EGLDisplay eglDisplay = eglGetDisplay(dpy);
> > ^
>
> Hi Alok,
>
> please take a look closely to the error log, because I think you haven't.
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
> gnueabi/qtbase/5.1.1-r0/qtbase-opensource-
> src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:275:50:
> error: cannot convert 'Display* {aka _XDisplay*}' to 'EGLNativeDisplayType
>
> Can be easily seen is a qtbase 5.1.1 error, not a Chromium error. qtbase is
> not required for Chromium.
>
> Please remove qt related things from your IMAGE_INSTALL_append and try
> again.
>
> Bests,
> Diego
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
Regards
Alok Kumar
[-- Attachment #2: Type: text/html, Size: 3961 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-21 3:14 ` Eric Nelson
2014-01-21 14:42 ` Diego
@ 2014-01-23 15:08 ` Alok Kumar
2014-01-23 15:14 ` Gary Thomas
2014-01-23 15:43 ` Eric Nelson
1 sibling, 2 replies; 19+ messages in thread
From: Alok Kumar @ 2014-01-23 15:08 UTC (permalink / raw)
To: Eric Nelson; +Cc: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2850 bytes --]
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@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
[-- Attachment #2: Type: text/html, Size: 4940 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-23 15:08 ` Alok Kumar
@ 2014-01-23 15:14 ` Gary Thomas
[not found] ` <CACoWYqXYmKAQ3L_9HjLvEEwJNQ56G+9ENcgup7t44D25EpTTcA@mail.gmail.com>
2014-01-23 15:43 ` Eric Nelson
1 sibling, 1 reply; 19+ messages in thread
From: Gary Thomas @ 2014-01-23 15:14 UTC (permalink / raw)
To: meta-freescale
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
------------------------------------------------------------
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
2014-01-23 15:08 ` Alok Kumar
2014-01-23 15:14 ` Gary Thomas
@ 2014-01-23 15:43 ` Eric Nelson
1 sibling, 0 replies; 19+ messages in thread
From: Eric Nelson @ 2014-01-23 15:43 UTC (permalink / raw)
To: Alok Kumar; +Cc: meta-freescale@yoctoproject.org
Hi Alok,
On 01/23/2014 08:08 AM, 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:
>
It looks like you're running this over the serial console...
Try setting the DISPLAY variable:
~/$ DISPLAY=:0 /usr/bin/chrome/chrome
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2014-01-24 21:30 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-22 18:40 3.10.17-1.0.0_beta meta-fsl-bsp-release layer alokcherryhills
-- strict thread matches above, loose matches on Subject: below --
2014-01-20 16:08 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 19:25 ` 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
[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
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.