anchor.diff:  
   Examples: host, amd64, cortex-m4, cortex-r7, avr, mipsel, etc.
   
  -Code generated for different architectures does not interoperate and cannot be linked together.
  -
  -- `M.ARCHS`: All available architectures for current toolchain
  -- `M.ARCH`: Current architecture for current toolchain
  -
   Good discussion on architecture naming here: http://clang.llvm.org/docs/CrossCompilation.html
   
   Variants
  
positive.code: Spores
  ------
  
  The spore is the fundamental unit of modular software artifact production in Moss.
  A spore describes how Moss produces artifacts from code in an architecture and toolchain independent fashion.
  
  Definition
  ~~~~~~~~~~
  
negative.code: Specialization
  ~~~~~~~~~~~~~~
  
  A given spore may produce artifacts for multiple architectures without requiring duplication of the spore definition.
  The architecture-specific 'specializations' are created from the base spore 'template'.
  Architecture-specific options and overrides can be specified through variables that 'overload' the base definition for the spore.
  
  Configuration
  ~~~~~~~~~~~~~
  
  Think menuconfig or kconfig.
  This is a formalized way to specify and use conditional boolean switches and string settings to specialize the artifacts produced by a spore.
  Configuration is the ideal way to provide the setting that are used during specialization to fine tune artifact production.
  
  Isolation
  ~~~~~~~~~
  