Ok, understood.
The thing is that I have built qt quite a number of times, for Raspbian,
Windows 32 bits, Linux 32 bits and so on. I never had to use this
option. From what you said I suppose qt 5.9.8 for iOS is not built with
it, so why do I have to specify it for 5.9.9, all the rest (JDK,
project) being equal ?
Philippe.
Le 11-08-2019 18:38, Thiago Macieira a écrit :
On Sunday, 11 August 2019 05:15:31 PDT maitai wrote:
FYI based on what you said I added -qt-zlib to configure options, and
now my app compiles and runs OK. I don't know if it is a normal option
for such a build
My regular recommendation is to never use the -qt-<libname> options.
You as
the app distributor should be aware of all the libraries you're
shipping, for
two very important reasons:
1) licensing. Most of those libraries are BSD-3-Clause, which means you
need
to list them and their copyright in your app's documentation. Qt can
help you
in this since there's a "qt_atribution.json" file next to each of the
third-
party libraries, so you can simply collect them all and include the
necessary
attributions in your documentation.
2) security. You must be aware of the libraries you can track CVEs
published
against them and update your build within a reasonable timeframe of the
fixes
being published by the upstream developers. Qt will not do this for
you.
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest