anchor.diff:  
   Gradle provides plugins for Visual Studio and Xcode. 
   
  -When used with the C++ plugins, Gradle will generate metadata files used by these IDEs. As much as possible, we've tried to make the IDE delegate to Gradle when compiling and linking C++ applications and libraries. 
  +When used with the C\++ plugins, Gradle will generate metadata files used by these IDEs. As much as possible, we've tried to make the IDE delegate to Gradle when compiling and linking C++ applications and libraries.
   
   JetBrains maintains a separate integration with CLion.
   
  
positive.code: 
  For a library, Gradle assumes its public headers are in `src/main/public`. Header files can be mixed into `src/main/cpp`, but these headers will be treated as private and not exposed to downstream consumers.
  
  Gradle assumes C++ source files end in `.cpp`, `.c+\+` or `.cc`. 
  
  [[cpp:declaring_dependencies]]
  == Declaring dependencies
  
negative.code: 
  ====
  
  Gradle's C\++ plugins add support for building applications and libraries written in C++. These plugins were https://blog.gradle.org/introducing-the-new-cpp-plugins[introduced in 2018] and we recommend new projects to use these plugins over <<native_software.adoc#native_binaries,the older Native plugins>>. This chapter makes heavy use of a https://github.com/gradle/native-samples[large collection of samples].
  
  [[cpp:features]]
  == Features
  