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: Sat, 21 Jun 2014 09:47:33 +0200	[thread overview]
Message-ID: <20140621074733.GD2117@jama> (raw)
In-Reply-To: <CACgAsMdguugQZiTiOo8aWaBZFCYnsWUtp7-0KWu7VdGvdBDCSA@mail.gmail.com>

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

On Fri, Jun 20, 2014 at 11:35:34PM -0400, Kevyn-Alexandre Paré wrote:
> On Fri, Jun 20, 2014 at 9:05 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Fri, Jun 20, 2014 at 08:22:39PM -0400, Kevyn-Alexandre Paré wrote:
> >> On Fri, Jun 20, 2014 at 7:48 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> > On Fri, Jun 20, 2014 at 06:30:09PM -0400, Kevyn-Alexandre Paré wrote:
> >> >> [1] I still don't understand why adding qtwebkit IMAGE_INSTALL make my
> >> >> build fail with:
> >> >> ERROR: qtwebkit not found in the base feeds
> >> >> LOG: http://pastebin.com/fx2Zi9vW
> >> >> Any clue what I'm doing wrong?
> >> >
> >> > Check which packages (if any) were created by qtwebkit recipe, if any
> >> > then read log.do_configure for possible clues.
> >> >
> >>
> >> qtwebkit-dbg and qtwebkit-dev is part of deploy rpm not qtwebkit? In
> >> pkgdata these only to have ".packaged"
> >> http://pastebin.com/0ugj2NVF
> >>
> >> log.do_configure:
> >> http://pastebin.com/cXWdDXmy
> >
> > The WebKit build was disabled for the following reasons:
> >     * ICU is required. To build QtWebKit with Qt 5 you need to build Qt
> >      5 with libICU support. Check for ICU support being mentioned in
> >      qtbase/config.summary.
> >
> 
> Yes you told me that in previous email I when to
> layers.openembedded.org to check
> 
> icu  53.1 International Component for Unicode libraries   openembedded-core
> 
> I add it in PACKAGECONFIG_append_pn-qtbase and IMAGE_INSTALL I thought
> it will be enough?
> 
> Obviously, I'm still missing somethink
> 
> qtbase/config.summary? you mean qtbase.inc?

I've just pasted it for you from the log.do_configure you sent me,
please _read_ it.

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.

> I see icu only mention in
> 
> poky/meta-qt5$ grep -Ri ICU *
> COPYING.MIT:FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
> NO EVENT SHALL THE
> licenses/DIGIA-TPLA-2.4:merchantability, fitness for a particular
> purpose, title and
> licenses/DIGIA-TPLA-2.4:merchantability, fitness for a particular
> purpose, title and
> recipes-qt/qt5/qtwebkit.inc:DEPENDS += "qtbase qtdeclarative icu
> ruby-native sqlite3 glib-2.0 libxslt"
> recipes-qt/qt5/qtbase.inc:# be aware that you need to add icu to build
> qtwebkit, default
> recipes-qt/qt5/qtbase.inc:PACKAGECONFIG[icu] = "-icu,-no-icu,icu"
> recipes-qt/qt5/qtbase-native.inc:    -no-icu \
> 
> My qtbase log.do_configure shows that it have been enable:
> http://pastebin.com/g7Lh5cPU
> 
> >> What's interesting or maybe not is that dgb and dev have empty rpm
> >> created and not the others?
> >> log.do_package_write_rpm
> >> http://pastebin.com/Cft9Uh3J
> >
> > -dbg and -dev are configured to create empty package
> > ALLOW_EMPTY_<pkgname>
> >
> 
> Aa, I'm only seeing it for these:
> 
> poky/meta-qt5$ grep -R ALLOW_EMPTY *
> recipes-qt/qt5/qtimageformats.inc:ALLOW_EMPTY_${PN} = "1"
> recipes-qt/qt5/qtbase.inc:ALLOW_EMPTY_${PN}-fonts = "1"

meta/conf/bitbake.conf:ALLOW_EMPTY_${PN}-dev = "1"
meta/conf/bitbake.conf:ALLOW_EMPTY_${PN}-dbg = "1"
meta/conf/documentation.conf:ALLOW_EMPTY[doc] = "Specifies if an output
package should still be produced if it is empty."

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

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

  reply	other threads:[~2014-06-21  7:47 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
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 [this message]
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=20140621074733.GD2117@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