From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qt5webkit: add missing icu dependency
Date: Mon, 12 Feb 2018 21:07:23 +0100 [thread overview]
Message-ID: <20180212210723.5148adca@windsurf.lan> (raw)
In-Reply-To: <20180211144926.jgne5lnzvlmoeq75@archlinux>
Hello,
On Sun, 11 Feb 2018 09:49:26 -0500, Ga?l PORTAY wrote:
> > Therefore, I don't see how you can fall into the situation where the
> > qt5webkit build is started without icu being already built.
> >
> > Could you explain ?
> >
>
> Well, I do not remember exactly the situation :/
>
> It happened in development. I assume I had a qtbase already build
> (certainly without ICU support). And then, I build qtwebkit running
> `make qt5webkit`, the issue happened.
>
> BTW, I made a quick look to qtwebkit, and it does not seem to call some
> Qt ICU symbols. It looks qtwebkit requires ICU for its own needs.
If that is truly the case, then qtwebkit should not select
BR2_PACKAGE_QT5BASE_ICU. Can you try to make a build with qt5webkit
enabled, but BR2_PACKAGE_QT5BASE_ICU disabled, and see what happens ?
Perhaps this select BR2_PACKAGE_QT5BASE_ICU needs to be turned into a
select BR2_PACKAGE_ICU + icu in QT5WEBKIT_DEPENDENCIES. Of course, make
sure to verify for Qt 5.6 and Qt 5.9. I hope you have some decent build
machines, because building qt5webkit is very long :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-12 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 2:03 [Buildroot] [PATCH 1/1] qt5webkit: add missing icu dependency Gaël PORTAY
2018-02-11 9:14 ` Thomas Petazzoni
2018-02-11 14:49 ` Gaël PORTAY
2018-02-12 20:07 ` Thomas Petazzoni [this message]
2018-02-12 20:54 ` Gaël PORTAY
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=20180212210723.5148adca@windsurf.lan \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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