All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: Abhijit Potnis <abhijit_potnis@mentor.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: meta-qt5, master, qtwebkit-examples build failure
Date: Fri, 4 Oct 2013 19:39:34 +0200	[thread overview]
Message-ID: <20131004173934.GL6240@jama> (raw)
In-Reply-To: <CALmOhgnnSusbb0OPO32TN9C8xQRmqMmW+ZDoEq7d2870JoQfRw@mail.gmail.com>

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

On Fri, Oct 04, 2013 at 12:50:17PM -0400, Trevor Woerner wrote:
> Thanks Martin,
> 
> On 4 October 2013 10:14, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Just lucky guess, do you have ICU enabled in qtbase?
> 
> That was a good guess!
> 
> It appears there's very important rule to know when using meta-qt5's
> master branch (i.e. 5.1.0):
> - if all you need is qtbase then ICU is not required and therefore not
> enabled (to save space)
> - if you need anything on top of qtbase then ICU must be enabled in
> qtbase's configuration
> 
> Do you think this would be a good thing to include in this layer's
> README (or is it somewhere I should have looked)?

There are few comments in qtbase.inc where people should look when they
are changing PACKAGECONFIG, but you're right that it isn't the place
where most people will look when they get misleading error like this
one.

# 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)

# gl or gles needs to be enabled in order to build qtdeclarative
# http://qt.gitorious.org/qt/qtdeclarative/commit/e988998a08b1420ed10bd02d9d4b3b8ed2289df9
PACKAGECONFIG_GL ?= "${@base_contains('DISTRO_FEATURES', 'opengl', 'gl',
'', d)}"

# accessibility is required to compile qtquickcontrols
PACKAGECONFIG[accessibility] = "-accessibility,-no-accessibility"

# gl or gles2 is needed in order to build qtdeclarative
# (qtdeclarative.do_configure fails to find quick module without)
PACKAGECONFIG[gl] = "-opengl desktop -no-eglfs,,virtual/libgl"

# depends on glib
PACKAGECONFIG[gstreamer] = "-gstreamer,-no-gstreamer,gstreamer"

# needed for qtdeclarative (qtdeclarative.do_configure fails to find
# quick module without)
PACKAGECONFIG[icu] = "-icu,-no-icu,${ICU}"

I'm thinking about using bb.warn when building qtbase without one of
them disabled, but again most people won't check qtbase build log when
they see "no such module qtwebkit" error.

I'll add at least some note to README file.

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

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

  reply	other threads:[~2013-10-04 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 13:03 meta-qt5, master, qtwebkit-examples build failure Trevor Woerner
2013-10-04 14:14 ` Martin Jansa
2013-10-04 16:50   ` Trevor Woerner
2013-10-04 17:39     ` Martin Jansa [this message]
2013-10-07 17:53       ` Denys Dmytriyenko
2013-10-08  4:28         ` Trevor Woerner
2013-10-08  4:37           ` Denys Dmytriyenko

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=20131004173934.GL6240@jama \
    --to=martin.jansa@gmail.com \
    --cc=abhijit_potnis@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=trevor.woerner@linaro.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 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.