| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Run autotests with minimal capabilities | Shane Kearns | 2010-05-10 | 1 | -0/+1 |
| | | | | | | | | | | | | The autotests were previously run with ALL-Tcb capability which gives them more access to the filesystem etc. than a typical Qt application. To have more realistic testing environmnent, tests are run with no capabilities other than those required for the Qt APIs they use. i.e. NetworkServices for network tests, None for others. Reviewed-by: Liang Qi | ||||
| * | Disable private unit tests when Qt is configured without | Rohan McGovern | 2009-07-09 | 1 | -0/+2 |
| | | | | | | | | | | | | | -developer-build, part 2. Some autotests use private (unexported) code, either because they're testing private classes or because that's the easiest way to test the public classes. Configuring Qt with `-developer-build' is needed for these tests. This commit fixes the tests so configuring without `-developer-build' only builds the tests which strictly use public API. | ||||
| * | Long live Qt! | Lars Knoll | 2009-03-23 | 1 | -0/+4 |
 |
index : qt/qt.git | |
| Qt 4.x. This repository is obsolete. |
| summaryrefslogtreecommitdiffstats |