mirror of
git://code.qt.io/qt/qt5.git
synced 2026-02-01 19:36:04 +08:00
d278e682c6
Previously configurations with -make examples in their configure args were building examples as part of the Qt library build. This has some downsides: - we don't build examples as a separate project, thus not ensuring that we build examples as our users would - qt cmake deployment api can't be used due to various limitations in our tooling Use the new qtbase instructions to instead build examples as a separate project in a separate build directory, after Qt is built and installed. This is similar to how we build standalone tests. The new instructions are activated by the StandaloneExamples features. It is opt-in as opposed to standalone tests, so we can disable the feature in case any regressions happen. Task-number: QTBUG-90820 Task-number: QTBUG-96232 Change-Id: I71b37b91ed09bcc0797841adf0df84cc0b111fd7 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@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)