Clean up the scope of configure scripts

- Remove unneeded elements from the special scope.
- Do not use the special scope for evaluating the condition.
- Only set up the special scope if we actually run the configure script.

Change-Id: I5e288fe839213a5226dae3be768c537c2919a15b
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

1 files changed, 2 insertions, 1 deletions

diff --git a/tests/auto/blackbox/testdata/configure/modules/definition/module.qbs b/tests/auto/blackbox/testdata/configure/modules/definition/module.qbs
index 60f442149..9f403d7fe 100644
--- a/tests/auto/blackbox/testdata/configure/modules/definition/module.qbs
+++ b/tests/auto/blackbox/testdata/configure/modules/definition/module.qbs
@@ -6,11 +6,12 @@ Module {
     Depends { name: 'cpp' }
     Probe {
         id: node
+        property stringList targetOS: qbs.targetOS
         property string result
         configure: {
             var cmd;
             var args;
-            if (qbs.targetOS.contains("windows")) {
+            if (targetOS.contains("windows")) {
                 cmd = qbs.windowsShellPath;
                 args = ["/c", "date", "/t"];
             } else {