Consider whether we should
- ship zlib as a separate dll, instead of linking it into Qt6Core
- remove qtbase/src/3rdparty/zlib, and rely on external sources
- zlib update (e.g. due to security issues found) won't require an update of qt sources & rebuild anymore
- Projects can make use of external zlib dll capabilities
- Windows does not provide zlib by default
- Users who build Qt on Windows would have to install & build zlib themselves, or get pre-built packages from somewhere. Would we provide these prebuilt packages?
- Every script packaging a qt app would need to be extended to also handle zlib1.dll
- dll hell? How compatible are different zlib1.dll's in the path?
- Is there a canonical zlib1.dll (which https://zlib.net/DLL_FAQ.txt suggests, but is not found on zlib.net)?
On macOS, our packages use the dynamic zlib that's available on the system:
Same on Linux:
|For Gerrit Dashboard: QTBUG-104524|
|464038,2||WIP CMake: Make it possible to install external 3rdparty dependencies||dev||qt/qtbase||Status: NEW||-2||0|