On 06/08/2017 05:22 PM, Cody P Schafer wrote:
Would it be reasonable to disable icu usage in meta-qt4 master while
switching pyro & morty to using the icu-native package?
Yes, absolutely.
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https:/
> I should give you a heads up: we (the yocto project) are going to remove qt4
> builds from the autobuilder altogether, sometime during this cycle. The repo
> will stay, and patches will be accepted though.
Thanks for the heads up.
> So it's up to you to solve these issues, but I wouldn't want t
On 06/07/2017 06:47 PM, Cody P Schafer wrote:
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 ne
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 poss
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:
|
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:
