OpenGL, ANGLE, ICU. Making the right choice.
-
I am doing a complete rebuild of Qt5.1.1 from source because of the rather large dependency list to distribute apps with. All of the targeted apps created are Windows Desktop 32 and 64 bit. Nothing web related.
From doing a fair amount of reading on the forums, it seems that both ANGLE and ICU are needed for web apps and Qt Quick (QML) apps - none of which is needed. Is there any other consideration for needing the above? Is the only way to get unicode support is by having ICU in the build? How did version 4.8 handle unicode?
-
If you pass -no-icu to configure, Qt will use it's default unicode backend, the same that was used in Qt4.
Remember that if you are not using ANGLE, your application will depend on OpenGL drivers installed on target machines.
-
And if you are not using OpenGL, hand -opengl desktop to configure. ANGLE has to be deactivated manually, too (-no-angle).
Once the webengine is switched over to Chromes blink, will these dependencies change for the better, i.e. shrink again? It does seem somewhat crazy, that even the tiniest of Qt programs created with the standard SDK comes in at about 50 megabytes. I had been working with Qt for over a year before ever considering to compile it myself, and back then it felt like quite a task. Therefore I assume that not everybody would be willing to recompile Qt, which renders it very unattractive for people newly introduced to Qt.
-
[quote author="sierdzio" date="1379479270"]If you pass -no-icu to configure, Qt will use it's default unicode backend, the same that was used in Qt4.
Remember that if you are not using ANGLE, your application will depend on OpenGL drivers installed on target machines.[/quote]
So then OpenGL Desktop with the assumption of NO OpenGL at all?
-
[quote author="thEClaw" date="1379488029"]And if you are not using OpenGL, hand -opengl desktop to configure. ANGLE has to be deactivated manually, too (-no-angle).
Once the webengine is switched over to Chromes blink, will these dependencies change for the better, i.e. shrink again? It does seem somewhat crazy, that even the tiniest of Qt programs created with the standard SDK comes in at about 50 megabytes. I had been working with Qt for over a year before ever considering to compile it myself, and back then it felt like quite a task. Therefore I assume that not everybody would be willing to recompile Qt, which renders it very unattractive for people newly introduced to Qt.[/quote]
Thanks, that's helpful
[quote]
Therefore I assume that not everybody would be willing to recompile Qt, which renders it very unattractive
[/quote]Edit: Indeed not intended for the faint of heart. It's taken a huge chunk of my week getting it right