mirror of
git://code.qt.io/qt/qt5.git
synced 2026-02-01 19:36:04 +08:00
15e37e994d
Currently the qtbase configure system always chooses to use SecureTransport on macOS configurations, even if a usable OpenSSL is found. As it is, there's no point to pass the OpenSSL location as a configure argument because one might get confused to think that Qt will be built with OpenSSL support (it won't). There is work in progress to allow building Qt Network with support for multiple ssl backends, but until that work is finished, remove the configure argument to avoid confusion. Change-Id: Ib91f0b85edc580145a78ab38aba7718e90a95240 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
Continuous Integration ====================== This directory contains files used by Qt's Continuous Integration system (Coin). pre-provisioning ---------------- Contains scripts which are used to install software to tier1 machines manually. E.g. Visual studio installation takes too long to be included to automatic provisioning of tier2 templates. provisioning ------------ Contains scripts that apply to different test machines in order to run automatic tests on them. For Windows scripts, make sure that the machine has "Set-ExecutionPolicy RemoteSigned -Force" set. (Run as admin in PowerShell)