Merged revisions 2647-2719 via svnmerge from

http://scons.tigris.org/svn/scons/branches/core

........
  r2649 | stevenknight | 2008-02-08 06:43:30 -0800 (Fri, 08 Feb 2008) | 3 lines

  Make the "bootstrap" copy directory relative to the script location
  regardless of where the user is when executing.
........
  r2650 | stevenknight | 2008-02-09 09:26:40 -0800 (Sat, 09 Feb 2008) | 3 lines

  Chdir back to the original directory before removing our temporary
  directory, to avoid "Permission denied" errors on Windows.
........
  r2651 | stevenknight | 2008-02-09 10:02:09 -0800 (Sat, 09 Feb 2008) | 3 lines

  Fix floating-point numbers confusing our notion of the .class
  files that will be generated in certain configurations.
........
  r2652 | stevenknight | 2008-02-09 10:26:48 -0800 (Sat, 09 Feb 2008) | 4 lines

  Issue 1868:  change the RootDir "lookup path" from '/' to '' so that
  looking up '/foo' returns the same node as looking up 'foo' when the
  current directory is the root.
........
  r2653 | stevenknight | 2008-02-09 11:16:17 -0800 (Sat, 09 Feb 2008) | 3 lines

  Issue 1902:  Document all the values that can now be fetched with GetOption.
  Additional formatting cleanups.
........
  r2654 | stevenknight | 2008-02-09 11:37:50 -0800 (Sat, 09 Feb 2008) | 3 lines

  Fix handling file names that contain substrings of multiple spaces
  when using ActionFactory instances like Copy() and Move().
........
  r2655 | stevenknight | 2008-02-09 13:36:14 -0800 (Sat, 09 Feb 2008) | 3 lines

  Issue 1898:  Fix use of a variable expansion in a source file name
  (like foo$OBJSUFFIX) when trying to match source builder suffixes.
........
  r2656 | stevenknight | 2008-02-09 20:58:32 -0800 (Sat, 09 Feb 2008) | 3 lines

  Issue 1903:  don't allow Java generics syntax to interfere with
  identifying an anonymous inner class.
........
  r2657 | stevenknight | 2008-02-09 21:02:37 -0800 (Sat, 09 Feb 2008) | 3 lines

  Left out the \w from the regular expression that matches generics,
  so we wouldn't match alphanumerics, only alphabetics.
........
  r2658 | stevenknight | 2008-02-09 23:33:03 -0800 (Sat, 09 Feb 2008) | 3 lines

  Issue 1899:  Enhance Chmod(), Delete(), Mkdir() and Touch() to take
  lists of Nodes or strings.
........
  r2659 | stevenknight | 2008-02-10 00:15:24 -0800 (Sun, 10 Feb 2008) | 4 lines

  Issue 1878:  Add comment lines to the generated config.h file describing
  the intent of the various #define/#undef lines.
  (David Cournapeau)
........
  r2660 | stevenknight | 2008-02-11 18:15:27 -0800 (Mon, 11 Feb 2008) | 3 lines

  Issue 1682:  Fix the ability to save and restore the ListOption value
  'all' in newer Python versions that have an all() built-in function.
........
  r2661 | stevenknight | 2008-02-27 07:25:18 -0800 (Wed, 27 Feb 2008) | 3 lines

  Issue 1919:  Optimize the SCons.Util.is_*() and SCons.Util.flatten()
  functions.  More efficient suffix selection in Selector.__call__() method.
........
  r2662 | stevenknight | 2008-02-28 06:43:29 -0800 (Thu, 28 Feb 2008) | 3 lines

  Fix SCons.Util.is_List() method to use the passed-in ListTypes variable.
  (Daniel Svensson)
........
  r2663 | stevenknight | 2008-02-28 06:57:44 -0800 (Thu, 28 Feb 2008) | 4 lines

  Issue 1884:  avoid an infinite loop when trying to use saved copies of
  the ToolInitializer objects that we use to initialize the env.Install()
  and env.InstallAs() methods.
........
  r2664 | garyo | 2008-02-28 07:25:25 -0800 (Thu, 28 Feb 2008) | 1 line

  Fix long-style command-line args in runtest.py (they were missing from getopt call).
........
  r2665 | garyo | 2008-02-28 09:31:42 -0800 (Thu, 28 Feb 2008) | 1 line

  runtest.py: Use qmtest instead of qmtest.py; newer QMTest releases may only have qmtest in /usr/bin.
........
  r2666 | stevenknight | 2008-02-28 12:10:02 -0800 (Thu, 28 Feb 2008) | 3 lines

  Remove dead code that was at one time apparently intended to grab the
  external environment's %INCLUDE% values.
........
  r2667 | stevenknight | 2008-02-28 12:16:40 -0800 (Thu, 28 Feb 2008) | 3 lines

  Move the regular expression and function that check for whether a
  construction variable name is legal from Util.py to Environment.py.
........
  r2668 | stevenknight | 2008-02-28 20:24:36 -0800 (Thu, 28 Feb 2008) | 2 lines

  Fix qmtest.py references (replace with qmtest) in tests and infrastructure.
........
  r2669 | stevenknight | 2008-02-28 20:27:05 -0800 (Thu, 28 Feb 2008) | 7 lines

  Speed up the SubstitionEnvironment.__setitem__() method by: 1) avoiding
  checking for whether the variable name is legal if it already exists; 2)
  use the regular expression directly when checking the form for illegality;
  3) more efficient check for whether a variable name is special.  Add a
  timing script so we can document why we implemented it as we did and
  revisit it in the future if need be.
........
  r2670 | stevenknight | 2008-02-28 20:51:44 -0800 (Thu, 28 Feb 2008) | 2 lines

  Add a shell script that generates context-diff output for review.
........
  r2671 | GregNoel | 2008-03-01 00:40:16 -0800 (Sat, 01 Mar 2008) | 1 line

  add test to env.__setitem__ benchmark
........
  r2672 | GregNoel | 2008-03-01 02:00:12 -0800 (Sat, 01 Mar 2008) | 1 line

  compatibility changes for env.__setitem__ benchmark
........
  r2673 | stevenknight | 2008-03-01 09:56:57 -0800 (Sat, 01 Mar 2008) | 3 lines

  Capture a vanilla copy of the Python 2.[45] timeit.py module, as a
  basis for being able to use this to time Python 2.2 (and earlier).
........
  r2674 | stevenknight | 2008-03-01 10:04:11 -0800 (Sat, 01 Mar 2008) | 3 lines

  Work around a race in the order in which we detect and report the build
  failures by letting the error messages show up in either order on stdout.
........
  r2675 | stevenknight | 2008-03-01 10:05:24 -0800 (Sat, 01 Mar 2008) | 3 lines

  Back-port the captured timeit.py module, and the env.__setitem__.py
  script itself, to Python versions before 2.3.
........
  r2676 | GregNoel | 2008-03-01 14:01:03 -0800 (Sat, 01 Mar 2008) | 1 line

  add banner information, remove inadvertent tabs
........
  r2677 | stevenknight | 2008-03-02 05:04:52 -0800 (Sun, 02 Mar 2008) | 3 lines

  Don't look for a Copyright string in the source-packaged bench/timeit.py
  module that we captured.
........
  r2678 | stevenknight | 2008-03-02 14:59:39 -0800 (Sun, 02 Mar 2008) | 6 lines

  Issue 1884:  Allow env.{Install,InstallAs}() to be replaced by user-
  supplied wrappers that call the underlying builder.

  Fix how environment cloning so it only clones dynamically-added method
  attributes that the user hasn't also overwritten explicity.
........
  r2679 | stevenknight | 2008-03-04 07:48:53 -0800 (Tue, 04 Mar 2008) | 3 lines

  Fix env.{Dir,Entry,File}() when the input is a list, broken last December
  when env.subst() was modified to return lists as-is.
........
  r2680 | stevenknight | 2008-03-04 08:24:06 -0800 (Tue, 04 Mar 2008) | 2 lines

  Fix printing Python Value Nodes in --debug=explain output.  (Jim Randall)
........
  r2681 | garyo | 2008-03-04 12:37:39 -0800 (Tue, 04 Mar 2008) | 1 line

  Make File(), Dir() and Entry() return lists when passed a sequence.
........
  r2682 | garyo | 2008-03-05 15:24:00 -0800 (Wed, 05 Mar 2008) | 1 line

  InstallBuilderWrapper and InstallBuilderWrapper should accept keyword args and pass them to the base builder, like other builders.
........
  r2683 | stevenknight | 2008-03-06 06:32:13 -0800 (Thu, 06 Mar 2008) | 2 lines

  Python 1.5.2 compatibility:  use apply() instead of **kw.
........
  r2684 | garyo | 2008-03-14 13:07:09 -0700 (Fri, 14 Mar 2008) | 1 line

  Fix QMTest problem with $TERM variable in user's environment causing test failures.
........
  r2685 | bdbaddog | 2008-03-14 13:16:20 -0700 (Fri, 14 Mar 2008) | 13 lines

  * Added java_where_includes - gets path list for java JDK's include dirs
  * Added java_where_java_home - gets  JAVA_HOME  path
  * Added path's to find java for sun's JDK rpm install to java_where_jar
  * moved paths() to be outside of java_ENV() routine and available for other routines to use as well as tests
  * set TERM to be dumb to fix broken readline causing massive failures on FC8 (only updated Gary's comments to include note about broken FC8 readline, as Gary committed the TERM just prior to my checkin)
  * Modified the following tests to use the above changes:
     * test/SWIG/SWIGOUTDIR.py
     * test/Java/swig-dependencies.py
     * test/Java/multi-step.py
     * test/Repository/Java.py
     * test/runtest/fallback.py  [ This test also has been changed to remove more than one qmtest in your PATH, previously it would only remove one path which had qmtest, my system had a local and a system version ]
........
  r2686 | stevenknight | 2008-03-15 20:50:07 -0700 (Sat, 15 Mar 2008) | 4 lines

  Add a warning about deprecating support for Python versions 1.5, 2.0
  and 2.1.  Fix the ability to SetOption('warn') so people can disable
  the warning by adding something to a SConscript file.
........
  r2687 | stevenknight | 2008-03-15 21:48:26 -0700 (Sat, 15 Mar 2008) | 3 lines

  Issue 1942:  Document the Dir(), File() and Entry() methods of Dir
  and File Nodes.  (Greg Noel)
........
  r2688 | GregNoel | 2008-03-16 00:05:04 -0700 (Sun, 16 Mar 2008) | 1 line

  Add parse_flags keyword option
........
  r2689 | stevenknight | 2008-03-16 00:32:33 -0700 (Sun, 16 Mar 2008) | 3 lines

  Print a message if we're skipping the build of a package because the
  necessary underlying tool doesn't exist.
........
  r2690 | stevenknight | 2008-03-16 00:40:28 -0700 (Sun, 16 Mar 2008) | 7 lines

  Add --warn=no-python-version to the $SCONSFLAGS variable when running
  tests under deprecated Python versions, so the warning doesn't interfere
  with running normal tests under those version.

  Have the test/python-version.py remove --warn=no-python-version from the
  $SCONSFLAGS variable, since it's explicitly testing that behavior.
........
  r2691 | stevenknight | 2008-03-16 08:20:54 -0700 (Sun, 16 Mar 2008) | 4 lines

  Handle ripple effects from setting $SCONSFLAGS to suppress the deprecation
  under older Python versions by commonizing and moving much of the logic
  in QMTest/TestSCons.py.
........
  r2692 | stevenknight | 2008-03-16 08:47:52 -0700 (Sun, 16 Mar 2008) | 5 lines

  Update the warning message for running under a deprecated Python
  version (text courtesy Greg Noel).  Make that warning a subclass of the
  DeprecatedWarning class, so the message can also be disabled by setting
  --warn=no-deprecated.
........
  r2693 | stevenknight | 2008-03-16 11:19:52 -0700 (Sun, 16 Mar 2008) | 4 lines

  Shorten the deprecated-python-version warning.
  Use sys.version_info to check, instead of hard-coded string comparisons.
  Edit the release note.
........
  r2694 | stevenknight | 2008-03-16 11:29:10 -0700 (Sun, 16 Mar 2008) | 3 lines

  Have the warning mention both that 2.2 is the base un-deprecated version
  and the version they're running without getting too wordy.
........
  r2695 | stevenknight | 2008-03-16 12:00:22 -0700 (Sun, 16 Mar 2008) | 2 lines

  Skip test/SWIG/SWIGOUTDIR.py if no installed jni.h files are found.
........
  r2696 | stevenknight | 2008-03-18 18:01:46 -0700 (Tue, 18 Mar 2008) | 2 lines

  Remove old, commented-out deprecation test code.
........
  r2697 | stevenknight | 2008-03-19 17:54:55 -0700 (Wed, 19 Mar 2008) | 2 lines

  Deprecate env.Copy() with a suppressable message.
........
  r2699 | stevenknight | 2008-03-20 08:20:22 -0700 (Thu, 20 Mar 2008) | 2 lines

  Move the debug-nomemoizer.py test to the test/Deprecated subdirectory.
........
  r2700 | stevenknight | 2008-03-20 08:37:51 -0700 (Thu, 20 Mar 2008) | 2 lines

  Issue 1954:  Adds deprecation warnings for --debug={dtree,stree,tree}.
........
  r2701 | stevenknight | 2008-03-23 00:33:25 -0700 (Sun, 23 Mar 2008) | 7 lines

  Add VariantDir() as a replacement for BuildDir().
  Change "build directory" references in text (comments and
  documentation) to "variant directory."
  Move and rename tests that named BuildDir in their path.
  Add a release note about the forthcoming deprecation of BuildDir().
  Add a test/Deprecated/BuildDir.py to track backwards compatibility.
........
  r2702 | stevenknight | 2008-03-24 11:23:39 -0700 (Mon, 24 Mar 2008) | 4 lines

  Change the VariantDir() and SConscrip "build_dir" keyword to "variant_dir."
  Still support "build_dir" for (you guessed it) backwards compatibility.
  Add documentation update and release note.
........
  r2703 | garyo | 2008-03-25 07:57:01 -0700 (Tue, 25 Mar 2008) | 1 line

  Improve Install error message when target and source list lengths don't match.
........
  r2704 | garyo | 2008-03-25 08:10:24 -0700 (Tue, 25 Mar 2008) | 1 line

  Allow executing main scons.py script without running scons, using standard if __name__==__main__ idiom.
........
  r2705 | stevenknight | 2008-03-26 08:51:58 -0700 (Wed, 26 Mar 2008) | 3 lines

  Update scripts that use {Source,Target}Signatures() to use Decider()
  or the default behavior.  Update test condition checks as necessary.
........
  r2706 | stevenknight | 2008-03-27 14:13:50 -0700 (Thu, 27 Mar 2008) | 2 lines

  Update some leftover uses of env.Copy() in some test scripts to env.Clone().
........
  r2707 | stevenknight | 2008-03-27 14:20:33 -0700 (Thu, 27 Mar 2008) | 6 lines

  Fix use of SetOption('warn') to disable warning messages.
  Refactor the Script.Main._setup_warn() function into
  Warnings.process_warn_strings().
  Split test/option--warn.py into separate test/option/warn-*.py scripts
  for the individual subtests it contained.
........
  r2708 | stevenknight | 2008-03-27 15:17:44 -0700 (Thu, 27 Mar 2008) | 5 lines

  Deprecate the {Target,Source}Signatures() functions and methods.
  Move the test scripts underneath the test/Deprecated directory.
  Update man page with the new --warn=* options (and some that
  were overlooked on previous checkins).  Add a release note.
........
  r2709 | stevenknight | 2008-03-27 23:22:38 -0700 (Thu, 27 Mar 2008) | 2 lines

  More conversion of env.Copy() calls to env.Clone().
........
  r2710 | stevenknight | 2008-03-28 00:09:40 -0700 (Fri, 28 Mar 2008) | 3 lines

  Test updates for old Python versions (1.5.2) now that we generate a
  warning message about the deprecation.
........
  r2711 | stevenknight | 2008-03-28 22:11:03 -0700 (Fri, 28 Mar 2008) | 3 lines

  Chmod the built packages in build/dist to 0644 so they're publicy readable
  when they're copied over to the snapshot system.
........
  r2712 | stevenknight | 2008-03-28 22:11:54 -0700 (Fri, 28 Mar 2008) | 3 lines

  Issue 1951:  have Copy() preserve file times and mode when copying
  over individual files.  (Leanid Nazdrynau)
........
  r2713 | stevenknight | 2008-03-29 06:49:27 -0700 (Sat, 29 Mar 2008) | 3 lines

  Don't bother checking for equivalent file access times.  Under system
  load it can vary because we do actually access the file.
........
  r2714 | GregNoel | 2008-03-29 17:24:25 -0700 (Sat, 29 Mar 2008) | 1 line

  Fix regression test using Python 1.5.2 on OS X
........
  r2715 | GregNoel | 2008-03-29 20:44:19 -0700 (Sat, 29 Mar 2008) | 1 line

  'Copy' conflicts with 'copy' on case-insensitive file systems
........
  r2716 | stevenknight | 2008-03-29 21:00:13 -0700 (Sat, 29 Mar 2008) | 3 lines

  Capture scripts for downloading and installing different versions of
  Python and SCons.
........
  r2717 | stevenknight | 2008-03-30 08:48:28 -0700 (Sun, 30 Mar 2008) | 3 lines

  Fix a regression in how subst_path() handles lists (like a ListOption)
  in expansions of things like $CPPDEFINES and $CPPPATH.
........
  r2718 | stevenknight | 2008-03-30 10:02:21 -0700 (Sun, 30 Mar 2008) | 6 lines

  User's Guide updates:
  --  Paragraph about deprecated BuildDir().
  --  Updated output using the jar -C option.
  --  Updated default environment Dump().
  --  Updated --debug=stacktrace output.
........
  r2719 | stevenknight | 2008-03-31 00:50:08 -0700 (Mon, 31 Mar 2008) | 2 lines

  Update the branch for 0.98.
........

6 files changed, 100 insertions, 76 deletions

diff --git a/doc/user/java.xml b/doc/user/java.xml
index 1876916..402d037 100644
--- a/doc/user/java.xml
+++ b/doc/user/java.xml
@@ -231,8 +231,8 @@
       % <userinput>scons -Q</userinput>
       javac -d classes -sourcepath prog1 prog1/Example1.java prog1/Example2.java
       javac -d classes -sourcepath prog2 prog2/Example3.java prog2/Example4.java
-      jar cf prog1.jar classes/Example1.class classes/Example2.class
-      jar cf prog2.jar classes/Example3.class classes/Example4.class
+      jar cf prog1.jar -C classes Example1.class -C classes Example2.class
+      jar cf prog2.jar -C classes Example3.class -C classes Example4.class
     </screen>
 
   </section>
diff --git a/doc/user/separate.in b/doc/user/separate.in
index 08bb986..be7e6c5 100644
--- a/doc/user/separate.in
+++ b/doc/user/separate.in
@@ -114,34 +114,46 @@ program using the F<build/foo.c> path name.
 
   It's often useful to keep any built files completely
   separate from the source files.
-  This is usually done by creating one or more separate
-  <emphasis>build directories</emphasis>
+  In &SCons;, this is usually done by creating one or more separate
+  <emphasis>variant directory trees</emphasis>
   that are used to hold the built objects files, libraries,
   and executable programs, etc.
-  for a specific flavor of build.
+  for a specific flavor, or variant, of build.
   &SCons; provides two ways to do this,
   one through the &SConscript; function that we've already seen,
-  and the second through a more flexible &BuildDir; function.
+  and the second through a more flexible &VariantDir; function.
+
+  </para>
+
+  <para>
+
+  One historical note:  the &VariantDir; function
+  used to be called &BuildDir;.
+  That name is still supported
+  but has been deprecated
+  because the &SCons; functionality
+  differs from the model of a "build directory"
+  implemented by other build systems like the GNU Autotools.
 
   </para>
 
   <section>
-  <title>Specifying a Build Directory as Part of an &SConscript; Call</title>
+  <title>Specifying a Variant Directory Tree as Part of an &SConscript; Call</title>
 
     <para>
 
-    The most straightforward way to establish a build directory
+    The most straightforward way to establish a variant directory tree
     uses the fact that the usual way to
     set up a build hierarchy is to have an
     &SConscript; file in the source subdirectory.
-    If you then pass a &build_dir; argument to the
+    If you then pass a &variant_dir; argument to the
     &SConscript; function call:
 
     </para>
 
     <scons_example name="ex1">
       <file name="SConstruct" printme="1">
-      SConscript('src/SConscript', build_dir='build')
+      SConscript('src/SConscript', variant_dir='build')
       </file>
       <file name="src/SConscript">
       env = Environment()
@@ -192,11 +204,11 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>Why &SCons; Duplicates Source Files in a Build Directory</title>
+  <title>Why &SCons; Duplicates Source Files in a Variant Directory Tree</title>
 
     <para>
 
-    &SCons; duplicates source files in build directories
+    &SCons; duplicates source files in variant directory trees
     because it's the most straightforward way to guarantee a correct build
     <emphasis>regardless of include-file directory paths,
     relative references between files,
@@ -209,14 +221,14 @@ program using the F<build/foo.c> path name.
     <para>
 
     The most direct reason to duplicate source files
-    in build directories
+    in variant directories
     is simply that some tools (mostly older vesions)
     are written to only build their output files
     in the same directory as the source files.
     In this case, the choices are either
     to build the output file in the source directory
-    and move it to the build directory,
-    or to duplicate the source files in the build directory.
+    and move it to the variant directory,
+    or to duplicate the source files in the variant directory.
 
     </para>
 
@@ -226,7 +238,7 @@ program using the F<build/foo.c> path name.
     relative references between files
     can cause problems if we don't
     just duplicate the hierarchy of source files
-    in the build directory.
+    in the variant directory.
     You can see this at work in
     use of the C preprocessor <literal>#include</literal>
     mechanism with double quotes, not angle brackets:
@@ -251,7 +263,7 @@ program using the F<build/foo.c> path name.
     will be found in the same directory hierarchy,
     and the simplest way to make sure
     that the right include file is found
-    is to duplicate the source files into the build directory,
+    is to duplicate the source files into the variant directory,
     which provides a correct build
     regardless of the original location(s) of the source files.
 
@@ -264,14 +276,14 @@ program using the F<build/foo.c> path name.
     it <emphasis>can</emphasis> usually be safely disabled.
     The next section describes
     how you can disable the duplication of source files
-    in the build directory.
+    in the variant directory.
 
     </para>
 
   </section>
 
   <section>
-  <title>Telling &SCons; to Not Duplicate Source Files in the Build Directory</title>
+  <title>Telling &SCons; to Not Duplicate Source Files in the Variant Directory Tree</title>
 
     <para>
 
@@ -287,15 +299,15 @@ program using the F<build/foo.c> path name.
     </para>
 
     <sconstruct>
-      SConscript('src/SConscript', build_dir='build', duplicate=0)
+      SConscript('src/SConscript', variant_dir='build', duplicate=0)
     </sconstruct>
 
     <para>
 
     When this flag is specified,
-    &SCons; uses the build directory
+    &SCons; uses the variant directory
     like most people expect--that is,
-    the output files are placed in the build directory
+    the output files are placed in the variant directory
     while the source files stay in the source directory:
 
     </para>
@@ -315,11 +327,11 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>The &BuildDir; Function</title>
+  <title>The &VariantDir; Function</title>
 
     <para>
 
-    Use the &BuildDir; function to establish that target
+    Use the &VariantDir; function to establish that target
     files should be built in a separate directory
     from the source files:
 
@@ -327,7 +339,7 @@ program using the F<build/foo.c> path name.
 
     <scons_example name="ex_builddir">
       <file name="SConstruct" printme="1">
-      BuildDir('build', 'src')
+      VariantDir('build', 'src')
       env = Environment()
       env.Program('build/hello.c')
       </file>
@@ -350,9 +362,9 @@ program using the F<build/foo.c> path name.
 
     <para>
 
-    When using the &BuildDir; function directly,
+    When using the &VariantDir; function directly,
     &SCons; still duplicates the source files
-    in the build directory by default:
+    in the variant directory by default:
 
     </para>
 
@@ -371,7 +383,7 @@ program using the F<build/foo.c> path name.
 
     <scons_example name="ex_duplicate_0">
       <file name="SConstruct" printme="1">
-      BuildDir('build', 'src', duplicate=0)
+      VariantDir('build', 'src', duplicate=0)
       env = Environment()
       env.Program('build/hello.c')
       </file>
@@ -396,11 +408,11 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>Using &BuildDir; With an &SConscript; File</title>
+  <title>Using &VariantDir; With an &SConscript; File</title>
 
     <para>
 
-    Even when using the &BuildDir; function,
+    Even when using the &VariantDir; function,
     it's much more natural to use it with
     a subsidiary &SConscript; file.
     For example, if the
@@ -411,7 +423,7 @@ program using the F<build/foo.c> path name.
 
     <scons_example name="example_builddir_sconscript">
       <file name="SConstruct">
-      BuildDir('build', 'src')
+      VariantDir('build', 'src')
       SConscript('build/SConscript')
       </file>
       <file name="src/SConscript" printme="1">
@@ -457,11 +469,11 @@ program using the F<build/foo.c> path name.
   <!--
 
   <section>
-  <title>Why You'd Want to Call &BuildDir; Instead of &SConscript;</title>
+  <title>Why You'd Want to Call &VariantDir; Instead of &SConscript;</title>
 
     <para>
 
-    XXX why call BuildDir() instead of SConscript(build_dir=)
+    XXX why call VariantDir() instead of SConscript(variant_dir=)
 
     </para>
 
diff --git a/doc/user/separate.xml b/doc/user/separate.xml
index 57acd48..57ade04 100644
--- a/doc/user/separate.xml
+++ b/doc/user/separate.xml
@@ -114,33 +114,45 @@ program using the F<build/foo.c> path name.
 
   It's often useful to keep any built files completely
   separate from the source files.
-  This is usually done by creating one or more separate
-  <emphasis>build directories</emphasis>
+  In &SCons;, this is usually done by creating one or more separate
+  <emphasis>variant directory trees</emphasis>
   that are used to hold the built objects files, libraries,
   and executable programs, etc.
-  for a specific flavor of build.
+  for a specific flavor, or variant, of build.
   &SCons; provides two ways to do this,
   one through the &SConscript; function that we've already seen,
-  and the second through a more flexible &BuildDir; function.
+  and the second through a more flexible &VariantDir; function.
+
+  </para>
+
+  <para>
+
+  One historical note:  the &VariantDir; function
+  used to be called &BuildDir;.
+  That name is still supported
+  but has been deprecated
+  because the &SCons; functionality
+  differs from the model of a "build directory"
+  implemented by other build systems like the GNU Autotools.
 
   </para>
 
   <section>
-  <title>Specifying a Build Directory as Part of an &SConscript; Call</title>
+  <title>Specifying a Variant Directory Tree as Part of an &SConscript; Call</title>
 
     <para>
 
-    The most straightforward way to establish a build directory
+    The most straightforward way to establish a variant directory tree
     uses the fact that the usual way to
     set up a build hierarchy is to have an
     &SConscript; file in the source subdirectory.
-    If you then pass a &build_dir; argument to the
+    If you then pass a &variant_dir; argument to the
     &SConscript; function call:
 
     </para>
 
     <programlisting>
-      SConscript('src/SConscript', build_dir='build')
+      SConscript('src/SConscript', variant_dir='build')
     </programlisting>
 
     <para>
@@ -187,11 +199,11 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>Why &SCons; Duplicates Source Files in a Build Directory</title>
+  <title>Why &SCons; Duplicates Source Files in a Variant Directory Tree</title>
 
     <para>
 
-    &SCons; duplicates source files in build directories
+    &SCons; duplicates source files in variant directory trees
     because it's the most straightforward way to guarantee a correct build
     <emphasis>regardless of include-file directory paths,
     relative references between files,
@@ -204,14 +216,14 @@ program using the F<build/foo.c> path name.
     <para>
 
     The most direct reason to duplicate source files
-    in build directories
+    in variant directories
     is simply that some tools (mostly older vesions)
     are written to only build their output files
     in the same directory as the source files.
     In this case, the choices are either
     to build the output file in the source directory
-    and move it to the build directory,
-    or to duplicate the source files in the build directory.
+    and move it to the variant directory,
+    or to duplicate the source files in the variant directory.
 
     </para>
 
@@ -221,7 +233,7 @@ program using the F<build/foo.c> path name.
     relative references between files
     can cause problems if we don't
     just duplicate the hierarchy of source files
-    in the build directory.
+    in the variant directory.
     You can see this at work in
     use of the C preprocessor <literal>#include</literal>
     mechanism with double quotes, not angle brackets:
@@ -246,7 +258,7 @@ program using the F<build/foo.c> path name.
     will be found in the same directory hierarchy,
     and the simplest way to make sure
     that the right include file is found
-    is to duplicate the source files into the build directory,
+    is to duplicate the source files into the variant directory,
     which provides a correct build
     regardless of the original location(s) of the source files.
 
@@ -259,14 +271,14 @@ program using the F<build/foo.c> path name.
     it <emphasis>can</emphasis> usually be safely disabled.
     The next section describes
     how you can disable the duplication of source files
-    in the build directory.
+    in the variant directory.
 
     </para>
 
   </section>
 
   <section>
-  <title>Telling &SCons; to Not Duplicate Source Files in the Build Directory</title>
+  <title>Telling &SCons; to Not Duplicate Source Files in the Variant Directory Tree</title>
 
     <para>
 
@@ -282,15 +294,15 @@ program using the F<build/foo.c> path name.
     </para>
 
     <programlisting>
-      SConscript('src/SConscript', build_dir='build', duplicate=0)
+      SConscript('src/SConscript', variant_dir='build', duplicate=0)
     </programlisting>
 
     <para>
 
     When this flag is specified,
-    &SCons; uses the build directory
+    &SCons; uses the variant directory
     like most people expect--that is,
-    the output files are placed in the build directory
+    the output files are placed in the variant directory
     while the source files stay in the source directory:
 
     </para>
@@ -310,18 +322,18 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>The &BuildDir; Function</title>
+  <title>The &VariantDir; Function</title>
 
     <para>
 
-    Use the &BuildDir; function to establish that target
+    Use the &VariantDir; function to establish that target
     files should be built in a separate directory
     from the source files:
 
     </para>
 
     <programlisting>
-      BuildDir('build', 'src')
+      VariantDir('build', 'src')
       env = Environment()
       env.Program('build/hello.c')
     </programlisting>
@@ -340,9 +352,9 @@ program using the F<build/foo.c> path name.
 
     <para>
 
-    When using the &BuildDir; function directly,
+    When using the &VariantDir; function directly,
     &SCons; still duplicates the source files
-    in the build directory by default:
+    in the variant directory by default:
 
     </para>
 
@@ -364,7 +376,7 @@ program using the F<build/foo.c> path name.
     </para>
 
     <programlisting>
-      BuildDir('build', 'src', duplicate=0)
+      VariantDir('build', 'src', duplicate=0)
       env = Environment()
       env.Program('build/hello.c')
     </programlisting>
@@ -389,11 +401,11 @@ program using the F<build/foo.c> path name.
   </section>
 
   <section>
-  <title>Using &BuildDir; With an &SConscript; File</title>
+  <title>Using &VariantDir; With an &SConscript; File</title>
 
     <para>
 
-    Even when using the &BuildDir; function,
+    Even when using the &VariantDir; function,
     it's much more natural to use it with
     a subsidiary &SConscript; file.
     For example, if the
@@ -415,7 +427,7 @@ program using the F<build/foo.c> path name.
 
     
     <programlisting>
-      BuildDir('build', 'src')
+      VariantDir('build', 'src')
       SConscript('build/SConscript')
       </programlisting>
 
@@ -448,11 +460,11 @@ program using the F<build/foo.c> path name.
   <!--
 
   <section>
-  <title>Why You'd Want to Call &BuildDir; Instead of &SConscript;</title>
+  <title>Why You'd Want to Call &VariantDir; Instead of &SConscript;</title>
 
     <para>
 
-    XXX why call BuildDir() instead of SConscript(build_dir=)
+    XXX why call VariantDir() instead of SConscript(variant_dir=)
 
     </para>
 
diff --git a/doc/user/troubleshoot.xml b/doc/user/troubleshoot.xml
index ca5ace8..dc90622 100644
--- a/doc/user/troubleshoot.xml
+++ b/doc/user/troubleshoot.xml
@@ -261,7 +261,7 @@
     <screen>
       % <userinput>scons</userinput>
       scons: Reading SConscript files ...
-      { 'BUILDERS': {'InstallAs': &lt;function InstallAsBuilderWrapper at 0x700000&gt;, 'Install': &lt;function InstallBuilderWrapper at 0x700000&gt;},
+      { 'BUILDERS': {'_InternalInstall': &lt;function InstallBuilderWrapper at 0x700000&gt;, '_InternalInstallAs': &lt;function InstallAsBuilderWrapper at 0x700000&gt;},
         'CONFIGUREDIR': '#/.sconf_temp',
         'CONFIGURELOG': '#/config.log',
         'CPPSUFFIXES': [ '.c',
@@ -293,7 +293,7 @@
         'INSTALL': &lt;function copyFunc at 0x700000&gt;,
         'LATEXSUFFIXES': ['.tex', '.ltx', '.latex'],
         'LIBPREFIX': 'lib',
-        'LIBPREFIXES': '$LIBPREFIX',
+        'LIBPREFIXES': ['$LIBPREFIX'],
         'LIBSUFFIX': '.a',
         'LIBSUFFIXES': ['$LIBSUFFIX', '$SHLIBSUFFIX'],
         'MAXLINELENGTH': 128072,
@@ -338,7 +338,7 @@
     <screen>
       C:\><userinput>scons</userinput>
       scons: Reading SConscript files ...
-      { 'BUILDERS': {'RES': &lt;SCons.Builder.BuilderBase instance at 0x700000&gt;, 'Object': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;, 'InstallAs': &lt;function InstallAsBuilderWrapper at 0x700000&gt;, 'PCH': &lt;SCons.Builder.BuilderBase instance at 0x700000&gt;, 'Install': &lt;function InstallBuilderWrapper at 0x700000&gt;, 'SharedObject': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;, 'StaticObject': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;},
+      { 'BUILDERS': {'_InternalInstall': &lt;function InstallBuilderWrapper at 0x700000&gt;, 'Object': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;, 'PCH': &lt;SCons.Builder.BuilderBase instance at 0x700000&gt;, 'RES': &lt;SCons.Builder.BuilderBase instance at 0x700000&gt;, 'SharedObject': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;, 'StaticObject': &lt;SCons.Builder.CompositeBuilder instance at 0x700000&gt;, '_InternalInstallAs': &lt;function InstallAsBuilderWrapper at 0x700000&gt;},
         'CC': 'cl',
         'CCCOM': &lt;SCons.Action.FunctionAction instance at 0x700000&gt;,
         'CCCOMFLAGS': '$CPPFLAGS $_CPPDEFFLAGS $_CPPINCFLAGS /c $SOURCES /Fo$TARGET $CCPCHFLAGS $CCPDBFLAGS',
@@ -1115,10 +1115,10 @@
       % <userinput>scons -Q --debug=stacktrace</userinput>
       scons: *** Source `prog.c' not found, needed by target `prog.o'.  Stop.
       scons: internal stack trace:
-        File "bootstrap/src/engine/SCons/Job.py", line 114, in start
-        File "bootstrap/src/engine/SCons/Script/Main.py", line 157, in prepare
+        File "bootstrap/src/engine/SCons/Job.py", line 131, in start
+        File "bootstrap/src/engine/SCons/Script/Main.py", line 169, in prepare
         File "bootstrap/src/engine/SCons/Taskmaster.py", line 169, in prepare
-        File "bootstrap/src/engine/SCons/Node/FS.py", line 2568, in prepare
+        File "bootstrap/src/engine/SCons/Node/FS.py", line 2551, in prepare
         File "bootstrap/src/engine/SCons/Node/__init__.py", line 349, in prepare
     </screen>
 
diff --git a/doc/user/variants.in b/doc/user/variants.in
index 2bdc394..9980b1d 100644
--- a/doc/user/variants.in
+++ b/doc/user/variants.in
@@ -49,7 +49,7 @@ is pretty smart about rebuilding things when you change options.
 
   <para>
 
-  The &build_dir; keyword argument of
+  The &variant_dir; keyword argument of
   the &SConscript; function provides everything
   we need to show how easy it is to create
   variant builds using &SCons;.
@@ -79,7 +79,7 @@ is pretty smart about rebuilding things when you change options.
 
     Export('env')
 
-    env.SConscript('src/SConscript', build_dir='build/$PLATFORM')
+    env.SConscript('src/SConscript', variant_dir='build/$PLATFORM')
     </file>
     <directory name="src"></directory>
     <directory name="src/hello"></directory>
@@ -140,7 +140,7 @@ is pretty smart about rebuilding things when you change options.
     <file name="SConstruct" printme="1">
     env = Environment(OS = ARGUMENTS.get('OS'))
     for os in ['newell', 'post']:
-        SConscript('src/SConscript', build_dir='build/' + os)
+        SConscript('src/SConscript', variant_dir='build/' + os)
     </file>
   </scons_example>
 
diff --git a/doc/user/variants.xml b/doc/user/variants.xml
index 6727859..3b570cd 100644
--- a/doc/user/variants.xml
+++ b/doc/user/variants.xml
@@ -49,7 +49,7 @@ is pretty smart about rebuilding things when you change options.
 
   <para>
 
-  The &build_dir; keyword argument of
+  The &variant_dir; keyword argument of
   the &SConscript; function provides everything
   we need to show how easy it is to create
   variant builds using &SCons;.
@@ -78,7 +78,7 @@ is pretty smart about rebuilding things when you change options.
 
     Export('env')
 
-    env.SConscript('src/SConscript', build_dir='build/$PLATFORM')
+    env.SConscript('src/SConscript', variant_dir='build/$PLATFORM')
   </programlisting>
 
   <para>
@@ -123,7 +123,7 @@ is pretty smart about rebuilding things when you change options.
     <file name="SConstruct" printme="1">
     env = Environment(OS = ARGUMENTS.get('OS'))
     for os in ['newell', 'post']:
-        SConscript('src/SConscript', build_dir='build/' + os)
+        SConscript('src/SConscript', variant_dir='build/' + os)
     </file>
   </scons_example>