Fixed command-line toolset configuration.

The toolsets must be defined in project-config.jam in order to allow the
toolset to be set on the command line.  This change is less than ideal
since the toolsets to test must be specified in two places, but it is
worth doing because limiting the toolsets on the command line is
extremely important.

Author: tee3

Jamroot

@@ -1,38 +1,25 @@
 import os ;
 import testing ;
 
-# configure a toolset and add it to the list of toolsets to test
-rule add-toolset ( name : version ? : path ? )
-{
-  local versioned-name = $(name) ;
-  if $(version)
-  {
-    versioned-name = $(name)-$(version) ;
-  }
-
-  toolset-choices += $(versioned-name) ;
-  using $(name) : $(version) : $(path) ;
-}
-
 # generate a list of toolsets to test
 local toolset-choices = ;
 
 # Default toolsets
 if [ os.name ] = NT
 {
-  add-toolset msvc ;
+  toolset-choices += msvc ;
 }
 else if [ os.name ] = CYGWIN
 {
-  add-toolset gcc ;
+  toolset-choices += gcc ;
 }
 else if [ os.name ] = LINUX
 {
-  add-toolset gcc ;
+  toolset-choices += gcc ;
 }
 else if [ os.name ] = MACOSX
 {
-  add-toolset darwin ;
+  toolset-choices += darwin ;
 }
 
 echo "building for the following toolsets:" ;

project-config.jam

@@ -0,0 +1,19 @@
+import os ;
+
+# Default toolsets
+if [ os.name ] = NT
+{
+  using msvc ;
+}
+else if [ os.name ] = CYGWIN
+{
+  using gcc ;
+}
+else if [ os.name ] = LINUX
+{
+  using gcc ;
+}
+else if [ os.name ] = MACOSX
+{
+  using darwin ;
+}