[oe] [yocto][meta-qt5][daisy] Error during bitbake of my image
Kevyn-Alexandre Paré
kapare at rogue-research.com
Mon Jun 23 16:21:24 UTC 2014
On Mon, Jun 23, 2014 at 10:01 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
> On Mon, Jun 23, 2014 at 09:40:28AM -0400, Kevyn-Alexandre Paré wrote:
<snip>
>> Here the way I check that icu is added as part of my image:
>> bitbake -e nirs-console-image | grep -n5 PACKAGECONFIG
>> 2560-# $B_pn-strace
>> 2561-# set /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/poky/meta/conf/distro/include/seperatebuilddir.inc:645
>> 2562-# "${SEPB}"
>> 2563-B_pn-strace="/home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/work/overo-poky-linux-gnueabi/nirs-console-image/1.0-r0/build"
>> 2564-#
>> 2565:# $PACKAGECONFIG [2 operations]
>> 2566-# set /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/poky/meta/conf/documentation.conf:308
>> 2567-# [doc] "This variable provides a means of enabling or
>> disabling features of a recipe on a per-recipe basis."
>> 2568-# _append[pn-qtbase]
>> /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/poky/meta-nirs/recipes-images/gumstix/nirs-console-image.bb:17
>> 2569-# " developer tests examples icu alsa-lib gles2
>> accessibility glib-2.0 tslib linuxfb sqlite3 "
>
> Are you trying to set PACKAGECONFIG_append_pn-qtbase from
> nirs-console-image.bb? That wont work you need to set it in distro or
> local.conf
Yes I was :( I was rereading ref manual
Configuration file: This method is identical to changing the block
through an append file except you edit your local.conf or
<mydistro>.conf file. As with append files previously described, you
can either completely override the variable:
PACKAGECONFIG_pn-<recipename>="f4 f5"
Or, you can just amend the variable:
PACKAGECONFIG_append_pn-<recipename> = " f4"
I Move my PACKAGECONFIG_append to my local.conf
Here my setup for now just trying to make it compile remove the gles
for now it was giving me errors...
bitbake -e qtbase | grep ^PACKAGECONFIG=
PACKAGECONFIG=" release dbus udev evdev widgets tools libs
openssl gl xcb xvideo xsync xshape xrender xrandr xfixes
xinput2 xinput xinerama xcursor gtkstyle xkb fontconfig freetype
jpeg libpng zlib pulseaudio developer tests examples icu
alsa-lib accessibility glib-2.0 tslib sqlite3
cat tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qtbase/5.2.1-r0/build/config.summary
| grep ICU
ICU .................... yes
it's compiling further then before and stop
meta-qt5/recipes-qt/qt5/qtdeclarative_5.2.1.bb, do_compile) failed
with exit code '1'
http://pastebin.com/qJAME8ew
_reading_ qtbase.inc qtwebkit depends on qtdeclarative and it depends
# gl or gles needs to be enabled in order to build qtdeclarative
The error is maybe not related to this but will work on adding gles to my image.
>
>> > Check config.summary in qtbase WORKDIR (where you built qtbase to be
>> > sure it was enabled) and check with bitbake -e that it's really in your
>> > PACKAGECONFIG for qtbase.
>>
>> My bad I didn't check in the WORKDIR only in meta-qt5...
>>
>> Check config.summary:
>> find tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qtbase/ -name config.summary
>> tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qtbase/5.2.1-r0/build/config.summary
>>
>> http://pastebin.com/gZ2Nqa5g
>>
>> Found that ICU is disable:
>> 27 Support enabled for:
>> 28 Accessibility .......... no
>> 29 ALSA ................... no
>> 30 CUPS ................... no
>> 31 FontConfig ............. no
>> 32 FreeType ............... qt
>> 33 Iconv .................. no
>> 34 ICU .................... no
>>
>> Clearly I'm doing something wrong!
>
> Yes, setting PACKAGECONFIG in wrong place.
thx
>
> bitbake -e qtbase | grep ^PACKAGECONFIG=
>
> is what you need to check.
>
>> [1] Will _read_ and try to make the config.summary change to yes...
>>
>> [2] When i'm setting my PACKAGECONFIG and i'm having one like:
>> PACKAGECONFIG[gles2] = "-opengl es2 -eglfs,,virtual/libgles2 virtual/egl"
>>
>> I'm suppose to set:
>> PACKAGECONFIG_append_pn-qtbase = " virtual/libgles2"
>> and not
>> PACKAGECONFIG_append_pn-qtbase = " gles2"
>> ?
>
> The later is less wrong, but setting
> PACKAGECONFIG_GL_pn-qtbase = "gles2"
> is even better.
For gles2 it's easy to know to use PACKAGECONFIG_GL but how do you
know for example when to put it where? I know it result all in
PACKAGECONFIG but I'm just curious?
ex: glib? PACKAGECONFIG_DISTRO or PACKAGECONFIG_SYSTEM?
Leaving for a week of vacancy & understanding a lot more thx to you!
BR,
-KA
More information about the Openembedded-devel
mailing list