anchor.diff:      }
   -------------------------------------------------------------------------------
   
  -==== Per-config +Name+ property (required) ====
  +==== Per-config Name property (required) ====
   
   The name of this configuration. Configuration names must be formatted in a
   dashed `platform-toolset` format. These two tokens form the first two in the
   quad `platform-toolset-variant-subvariant` system Tundra uses to id builds.
   
  -==== Per-config +Tools+ property (required) ====
  +==== Per-config Tools property (required) ====
   
   A list of tools this configuration uses. A tool specification is either a
   string, indicating that the defaults for that tool are to be used, or a table
  
positive.code: Used with care this is a powerful way of letting users customize variables per
  configuration and then glue everything together with a simple template.
  
  // vim: set syntax=asciidoc
  
  
negative.code: Projects can add their own tool scripts via a +ToolsetDirs+ array property in
  the +Build+ block.
  
  ==== Per-config DefaultOnHost property (optional) ====
  
  If present, this config will be built by default when the host platform matches
  the string. This is convenient to have the host's native configuration build
  in the default variant when you just type `tundra` in the shell.
  
  ==== Per-config Env property (optional) ====
  
  If present, must be set to a table. This table contains key-value bindings to
  apply to the environment for this configuration. This typically includes things
  such as include paths (`CPPPATH`), C preprocessor defines (`CPPDEFS`) and C
  compiler options (`CCOPTS`).
  
  -----------------------------------------------------------------------------
  Build {
    Configs = {
      { Name = "foo-bar", Env = { CPPDEFS = { "FOO", "BAR=BAZ", ... } }, },
      ...
    },
  }
  -----------------------------------------------------------------------------
  
  ==== Per-config Inherit property (optional) ====
  
  If present, must be set to a table. This table will be scanned for values if
  they are not present in the Config table itself. This is useful to group common
  