Shoehorn dart2js into the SDK.

dart/tools/testing/dart/test_suite.dart

Index: dart/tools/testing/dart/test_suite.dart
diff --git a/dart/tools/testing/dart/test_suite.dart b/dart/tools/testing/dart/test_suite.dart
index 0b0ac483f115b7131398805fa24768f9b275a7bf..1c213725856bc7ed31af326576c323c6327b7eed 100644
--- a/dart/tools/testing/dart/test_suite.dart
+++ b/dart/tools/testing/dart/test_suite.dart
@@ -1233,10 +1233,14 @@ class TestUtils {
       case 'dartc':
         return 'compiler/bin/dartc$suffix';
       case 'dart2js':
+        var prefix = '';
+        if (configuration['use_sdk']) {
+          prefix = 'dart-sdk/bin/';

[Bill Hesse, 2012/04/30 15:21:32]

Shouldn't the --use_sdk option apply to frog and to vm as well?  There are
copies of the vm and the frog compiler.  Isn't it the right thing to do to
enable the new option for all appropriate targets?

[ahe, 2012/05/02 10:32:17]

Frog is EOL and the frog/bin vs dart-sdk/bin is a further complication.

dartc is not in the SDK.

So the only remaining thing is the VM. I don't know if they plan to use this
option or not, but I would prefer not changing anything that is not tested (as I
do with the dart2js build bot).

+        }
         if (configuration['host_checked']) {
-          return 'dart2js_developer$suffix';
+          return '${prefix}dart2js_developer$suffix';
         } else {
-          return 'dart2js$suffix';
+          return '${prefix}dart2js$suffix';
         }
       case 'frog':
         return 'frog/bin/frog$suffix';
@@ -1251,11 +1255,7 @@ class TestUtils {
       case 'dartc':
         return 'compiler/bin/dartc$suffix';
       case 'dart2js':
-        if (configuration['host_checked']) {
-          return 'dart2js_developer$suffix';
-        } else {
-          return 'dart2js$suffix';
-        }
+        return executableName(configuration);
       case 'frog':
         return 'frog/bin/frog$suffix';
       default: