anchor.diff:  
   Toolchain specific dependencies would automatically inherit the appropriate toolchain prefix.
   
  -Some use cases may require that toolchain be specialized for certain spores by architecture. That is, a given spore might have to be built a special way for a particular architecture. I think this could be done via target specific variables.
  +Some use cases may require that toolchain be specialized for certain spores by platforms. That is, a given spore might have to be built a special way for a particular platform. I think this could be done via target specific variables.
  
positive.code: - executables -> `M.EXECUTABLE.PATH`
  
  Headers located in `M.HEADER.PATH` are automatically included as part of
  the system include path when building spore products. Libraries located in
  `M.LIB.PATH` are included as part of the library search path when linking
  spore products.
  
  An example `moss.build` structure might look something like this:
  
  
negative.code: 				libcore.a
  				libcrypto.a
  
  Moss assumes that header files are shared across all platforms and
  toolchains. Any platform-specific header files are an internal
  implementation detail of the source code for a spore that defines them.
  
  == Recursive vs Inclusive
  
  There are some high-level considerations to make. Do we use any amount of
  recursive make to help with iteration over toolchains, platforms, or
  possibly even individual spores? It may simplify some things, but the
  performance tradeoffs are unknown. As little recursion as possible is the
  general design goal.
  