[yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

Cody P Schafer dev at codyps.com
Wed Jun 7 08:47:32 PDT 2017

Yep, for `master` that is certainly true.

For `morty` & `pyro` though, meta-qt4 could keep working by using icu-native.

The source of this issue being qt4's general incompatibility with C++
11 (we build with c++98 because of build errors with the newer std)
makes me wonder if it will even be possible to continue supporting qt4
going forward.

This may turn out like the openssl conflicts in that we'll need to
disable qt4's use of icu entirely.

On Wed, Jun 7, 2017 at 8:24 AM, Alexander Kanavin
<alexander.kanavin at linux.intel.com> wrote:
> On 06/07/2017 07:19 AM, Cody P Schafer wrote:
>> Previously, qt4-native would use the system icu to build.
>> Trying to build against a system ICU 59, however, fails with this root
>> error:
>> | In file included from /usr/include/unicode/uversion.h:30:0,
>> |                  from tools/qlocale_icu.cpp:46:
>> | /usr/include/unicode/umachine.h:347:13: error: ‘char16_t’ does not name
>> a type; did you mean ‘wchar_t’?
>> |      typedef char16_t UChar;
>> |              ^~~~~~~~
>> |              wchar_t
> We will introduce icu 59 to oe-core at some point (in fact, I have a patch
> queued), and then this fix will no longer work.
> You need to fix Qt4 itself.
> Alex

More information about the yocto mailing list