5573ca3599
This is meant to allow the buildsystem to add additional paths (for e.g. QML imports) while still allowing the application to pick up the paths where e.g. Qt's plugins are located – without having to query qtpaths or the build system to locate them first, and to then also add them to qt.conf. QLibraryInfo::paths will return a list containing any values provided in qt.conf, followed by the value that would have been provided if there were no qt.conf file. If no value is provided at all for a given key in qt.conf, QLibraryInfo::path will behave as if no qt.conf file was provided, instead of using LocationInfo::defaultValue. For now, this is considered to be internal only, and won't be documented. Change-Id: Ic74c66b5cbde605b43336cd88c3f909999381f46 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.