Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [yocto][meta-qt5][daisy] Error during bitbake of my image
Date: Fri, 20 Jun 2014 10:13:07 +0200	[thread overview]
Message-ID: <20140620081307.GW2117@jama> (raw)
In-Reply-To: <CACgAsMdCCZNcNwmLF-BEEcY=JuTtMCPL9K+9TEhCKU7Q+DAs4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3425 bytes --]

On Thu, Jun 19, 2014 at 08:38:19PM -0400, Kevyn-Alexandre Paré wrote:
> On Thu, Jun 19, 2014 at 7:21 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Thu, Jun 19, 2014 at 07:06:08PM -0400, Kevyn-Alexandre Paré wrote:
> >> I'm a bit further but still have some interrogations?
> >>
> >> ERROR: qtwebkit not found in the base feeds (overo armv7a-vfp-neon
> >> armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5
> >> armv4 arm noarch any all)
> >>
> >> I'm having these included in my image:
> >>
> >>   ruby \
> >>   qtbase \
> >>   qtbase-fonts \
> >>   qtbase-fonts-ttf-vera \
> >>   qtbase-fonts-ttf-dejavu \
> >>   qtbase-fonts-pfa \
> >>   qtbase-fonts-pfb \
> >>   qtbase-fonts-qpf \
> >>   qtbase-tools-dbg \
> >>   qtbase-plugins-dbg \
> >>   qtbase-tools \
> >>   qtbase-plugins \
> >>   qtbase-mkspecs \
> >>   qtbase-dev \
> >>   qtdeclarative-qmlplugins-dbg \
> >>   qtdeclarative-tools-dbg \
> >>   qtdeclarative-plugins-dbg \
> >>   qtdeclarative-qmlplugins \
> >>   qtdeclarative-tools \
> >>   qtdeclarative-plugins \
> >>   qtdeclarative-mkspecs \
> >>   qtdeclarative-dbg \
> >>   qtdeclarative-dev \
> >>   qtdeclarative \
> >>   qtquick1-qmlplugins-dbg \
> >>   qtquick1-tools-dbg \
> >>   qtquick1-plugins-dbg \
> >>   qtquick1-qmlplugins \
> >>   qtquick1-tools \
> >>   qtquick1-plugins \
> >>   qtquick1-mkspecs \
> >>   qtquick1-dbg \
> >>   qtquick1-dev \
> >>   qtquick1 \
> >>   qttools-tools-dbg \
> >>   qttools-tools \
> >>   qttools-mkspecs \
> >>   qttools-dbg \
> >>   qttools-dev \
> >>   qttools \
> >>   qtwebkit \
> >>
> >> [1] Why the bitbake qtwebkit is working but not when I'm including it
> >> in my image?
> >
> > What PACKAGECONFIG values are you using (especially for qtbase)?
> 
> Sorry for a lot of newbie questions... But I have not play with PACKAGECONFIG
> I didn't change PACKAGECONFIG. The only thing I was doing was to add
> previous list of packages to IMAGE_INSTALL +=
> 
> >
> > carefully read comments in qtbase.inc
> >
> 
> Reading it make me remember that what I want to do, enable qtquick,
> that depends on qtquick1.inc:
> 
> DEPENDS += "qtscript qtsvg qtxmlpatterns qtwebkit"
> 
> I thought that simply adding them to the IMAGE_INSTALL will be enough
> 
> Then in qtbase.inc:
> 
> # separate some parts of PACKAGECONFIG which are often changed
> # be aware that you need to add icu to build qtwebkit, default
> # PACKAGECONFIG is kept rather minimal for people who don't need
> # stuff like webkit (and it's easier to add options than remove)
> 
> So could this be because I'm not adding the icu?
> 
> PACKAGECONFIG[icu] = "-icu,-no-icu,icu"
> 
> So from a old email you respond:
> https://www.mail-archive.com/yocto@yoctoproject.org/msg16316.html
> 
> I think that if I want to enable the icu I need to add???
> PACKAGECONFIG vim ??= "icu" in my local.conf or could I add it
> somewhere else? like in the recipe of my image?

PACKAGECONFIG_append_pn-qtbase = " icu"

You'll probably want also gl and accessibility.

> Still confuse about that part...
> 
> BR,
> 
> -KA
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-06-20  8:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 18:49 [yocto][meta-qt5][daisy] Error during bitbake of my image Kevyn-Alexandre Paré
2014-06-19 19:26 ` Martin Jansa
2014-06-19 20:32   ` Kevyn-Alexandre Paré
2014-06-19 21:08     ` Martin Jansa
2014-06-19 21:34       ` Kevyn-Alexandre Paré
2014-06-19 23:06         ` Kevyn-Alexandre Paré
2014-06-19 23:21           ` Martin Jansa
2014-06-20  0:38             ` Kevyn-Alexandre Paré
2014-06-20  8:13               ` Martin Jansa [this message]
2014-06-20 22:30                 ` Kevyn-Alexandre Paré
2014-06-20 23:48                   ` Martin Jansa
2014-06-21  0:22                     ` Kevyn-Alexandre Paré
2014-06-21  0:32                       ` Kevyn-Alexandre Paré
2014-06-21  1:05                       ` Martin Jansa
2014-06-21  3:35                         ` Kevyn-Alexandre Paré
2014-06-21  7:47                           ` Martin Jansa
2014-06-23 13:40                             ` Kevyn-Alexandre Paré
2014-06-23 14:01                               ` Martin Jansa
2014-06-23 16:21                                 ` Kevyn-Alexandre Paré
2014-06-23 16:51                                   ` Martin Jansa
2014-07-04 15:00                                     ` Kevyn-Alexandre Paré
2014-07-04 15:37                                       ` Kevyn-Alexandre Paré

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=20140620081307.GW2117@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox