Re: [Development] Does Qt 5.6 still depend on ICU?

2016-05-08 Thread Thiago Macieira
On domingo, 8 de maio de 2016 12:20:24 PDT Roland Winklmeier wrote:
> > Looks like a mistake.
> 
> Do you want me to raise a bug report?

Yes, please.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Does Qt 5.6 still depend on ICU?

2016-05-08 Thread Roland Winklmeier
On 05/08/2016 01:10 AM, Thiago Macieira wrote:
> On sábado, 7 de maio de 2016 23:25:16 PDT Roland Winklmeier wrote:
>> From wiki pages  (https://wiki.qt.io/Qt_5.6_Tools_and_Versions and
>> https://wiki.qt.io/Building_Qt_5_from_Git), I understood that, ICU is
>> only required for QtWebkit. I also learned that the ICU version shipped
>> in Qt 5.6.0 is 56.1.
>>
>> However, I found the following facts a bit inconsistent:
>> * Windows is actually shipping 54.1 instead of 56.1. Was the upgrade
>> missed or is this on purpose? To me it is a minor issue, but I'm curious.
> 
> Looks like a mistake.

Do you want me to raise a bug report?

>> Now my question:
>> Is ICU mandatory for all platforms or maybe only for Linux? Ideally I
>> could just skip shipping it in my installer, since I'm using a custom
>> Qt5 build on my Debian server (I did not yet manage to use the official
>> installer on a headless server with an install script). But I want to be
>> sure, what features I'm loosing before any decision. ?
> 
> It's mandatory for none. You can choose if you build from sources, but note 
> that the POSIX fallback for Unix systems is of much lower quality.
> 
> The choices made for the binary builds are just that: choices.
> 

Thanks a lot. Now it is much clearer to me. I'll follow the official
release binaries choice and link my custom Linux build against ICU.

Cheers Roland
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Does Qt 5.6 still depend on ICU?

2016-05-08 Thread Kai Koehne


> -Ursprüngliche Nachricht-
> Von: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] Im Auftrag von Alexander Nassian
> Gesendet: Sonntag, 8. Mai 2016 00:56
> An: Roland Winklmeier <roland.m.winklme...@gmail.com>
> Cc: development@qt-project.org
> Betreff: Re: [Development] Does Qt 5.6 still depend on ICU?
> 
> As far as I know Chromium also depends on ICU and without WebKit or
> WebEngine you may but need not to use ICU.

Qt WebEngine  / Chromium on Windows builds with a statically linked version 
of ICU by default though, so there's no need to ship the ICU dll's for Qt 
WebEngine - just the icudtl.dat file .

Regards

Kai

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Does Qt 5.6 still depend on ICU?

2016-05-07 Thread Thiago Macieira
On sábado, 7 de maio de 2016 23:25:16 PDT Roland Winklmeier wrote:
> From wiki pages  (https://wiki.qt.io/Qt_5.6_Tools_and_Versions and
> https://wiki.qt.io/Building_Qt_5_from_Git), I understood that, ICU is
> only required for QtWebkit. I also learned that the ICU version shipped
> in Qt 5.6.0 is 56.1.
> 
> However, I found the following facts a bit inconsistent:
> * Windows is actually shipping 54.1 instead of 56.1. Was the upgrade
> missed or is this on purpose? To me it is a minor issue, but I'm curious.

Looks like a mistake.

> * Official Windows QtCore binary is not linked against ICU libraries (at
> least from what I can see in dependency walker). Does it link at runtime?

No. The build for Windows is using the Windows API so you can ship smaller 
builds without ICU.

> * Official Linux QtCore binary in contrast is linked against ICU
> (verified with ldd).

The Linux build is linking against ICU because there's no fallback API of 
similar quality. And also because all Linux distros have ICU anyway.

> * Official OS X QtCore binary again is not linked against ICU.

Like Windows, OS X has a fallback API. In fact, Apple's API is almost a direct 
mapping of ICU's API.

> Now my question:
> Is ICU mandatory for all platforms or maybe only for Linux? Ideally I
> could just skip shipping it in my installer, since I'm using a custom
> Qt5 build on my Debian server (I did not yet manage to use the official
> installer on a headless server with an install script). But I want to be
> sure, what features I'm loosing before any decision. ?

It's mandatory for none. You can choose if you build from sources, but note 
that the POSIX fallback for Unix systems is of much lower quality.

The choices made for the binary builds are just that: choices.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Does Qt 5.6 still depend on ICU?

2016-05-07 Thread Alexander Nassian
As far as I know Chromium also depends on ICU and without WebKit or WebEngine 
you may but need not to use ICU. But I sadly don't know if and what features 
are (internally) missing if Qt is not built with ICU - for our applications we 
always have to build it with because of WebKit/WebEngine.

Beste Grüße / Best regards,
Alexander Nassian

> Am 07.05.2016 um 23:25 schrieb Roland Winklmeier 
> :
> 
> Dear Qt Devs,
> 
> I'm currently preparing installers for a cross platform application
> (Win, Linux, OSX). I have investigated, which dependencies apart from
> the Qt5 libraries themselves are need to be shipped as well. But I'm a
> bit confused about the role of ICU.
> 
> From wiki pages  (https://wiki.qt.io/Qt_5.6_Tools_and_Versions and
> https://wiki.qt.io/Building_Qt_5_from_Git), I understood that, ICU is
> only required for QtWebkit. I also learned that the ICU version shipped
> in Qt 5.6.0 is 56.1.
> 
> However, I found the following facts a bit inconsistent:
> * Windows is actually shipping 54.1 instead of 56.1. Was the upgrade
> missed or is this on purpose? To me it is a minor issue, but I'm curious.
> * Official Windows QtCore binary is not linked against ICU libraries (at
> least from what I can see in dependency walker). Does it link at runtime?
> * Official Linux QtCore binary in contrast is linked against ICU
> (verified with ldd).
> * Official OS X QtCore binary again is not linked against ICU.
> 
> Now my question:
> Is ICU mandatory for all platforms or maybe only for Linux? Ideally I
> could just skip shipping it in my installer, since I'm using a custom
> Qt5 build on my Debian server (I did not yet manage to use the official
> installer on a headless server with an install script). But I want to be
> sure, what features I'm loosing before any decision. ?
> 
> *guess mode on*
> I guess, ICU was shipped previously because of QtWebkit. Since QtWebkit
> is no longer shipped in official installers, could ICU also be removed?
> I know what ICU is, but why is it shipped without linking against it?
> *guess mode off*
> 
> Cheers Roland
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development