anchor.diff:  https://github.com/gradle/native-samples/tree/master/cpp/simple-library[See a sample].
   
   [[cpp:variants]]
  -== C++ Binary Variants
  +== Configure for different targets
   
   From a C++ library or application, Gradle generates what we call a binary.  This binary is a variant of a component which has been assigned a particular build type (e.g., debug) and target machine (e.g., 32-bit Windows). Only binaries that may be built on the current host are generated by Gradle.
   
  
positive.code: [[cpp:unit_test]]
  == Unit Testing support
  
  Unit testing support is very limited right now. Gradle makes no assumptions about the type of unit testing framework being used. 
  
  In the future, Gradle make come with support out-of-the-box for a particular testing framework or make it easier to integrate your own.
  
  https://github.com/gradle/native-samples/tree/master/cpp/library-with-tests[See a sample].
  
  [[cpp:limitations]]
  == Limitations
  
negative.code: * Automatic discovery of popular tool chains (Visual C++, GCC, Clang).
  * Integration with https://gradle.com/build-scans/[build scans].
  
  [[cpp:overview]]
  == Plugin overview
  
  Unlike the <<native_software.adoc#native_binaries,software model native plugins>>, the new C++ plugins rely on a familiar DSL and configuration model. 
  
  When the C++ plugin is applied to the project, Gradle registers an extension for the type of project (application or library). All configuration is done through this extension or the tasks registered by the plugin.
  
  [[cpp:incremental_compilation]]
  == Incremental Compilation
  