Adds the libPods.a and target derivatives back as targets in the Pods 
project.  The integration libraries are simple containers linked with 
all of the per spec libraries to create a single library for the user 
project to link with.  The xcconfig file for the integration library 
merges namespaced config settings for all dependent specs for use by 
the user project.

* master:
  Release 0.19.1
  [Integration] Update version in fixtures
  CHANGELOG [skip ci]
  [TargetInstaller] Create unique hash instances for the build settings
  [Generator::Xcconfig] Add inherited to GCC_PREPROCESSOR_DEFINITIONS
  Changelog [ci skip]

Conflicts:
	lib/cocoapods/generator/xcconfig.rb

Closes #1014

See #903

Closes #1012

Merge branch 'dedicated-targets' of https://github.com/jasl8r/CocoaPods into jasl8r-dedicated-targets

* 'dedicated-targets' of https://github.com/jasl8r/CocoaPods:
  Support xcconfig files per Podfile target
  Add specs to libraries for non-integrated targets
  Only add a single Manifest.lock phase when dealing with multiple specs
  Identify copy build phase by spec name
  Add per-spec static library targets

Closes #998

Closes #1004

Xcconfig files are generated for every library target and target 
defined in the Podfile.  However, only the Podfile target xcconfig 
files are added to the user project.  This required tracking all the 
libraries as well as the Podfile targets through the installation and 
integration procedures.

See #971

See #985

Closes #985

Static library targets are created for each combination of user-target
and spec dependency.  This addresses issue #841, although likely not 
entirely.

New command podfile-info - Shows information on installed Pods #855

Added hint about updating CocoaPods installation when Podfile.lock and Manifest.lock are not in sync