This gives us an entry point for disabling specific project.yml
validations that sometimes shouldn't apply. The first example is
missingConfigs, which, if you use your .yml file in multiple projects,
can be too strict if the projects have different top level
configurations.
XcodeGen now supports "External Build Tool" target type (internally called
PBXLegacyTarget in Xcode). This is implied when the target provides a
`LegacyTarget` field in its spec.
PBXLegacyTargets are just like normal targets but the `isa` is different
and they have a notion of a buildTool. Most of the target logic doesn't
have to change.
* Add commandlineArguments to XcodeGenKit Scheme specifications
* Update xcproj reference, format code, cleanup usage of
commandlineArguments in ProjectGenerator
* Update docs, CHANGELOG and equality checks in Scheme.swift
* Doc update
* Update fixture tests to have command line arguments. Fix remaining issue
with Scheme creation through "Test Scheme"
* Resolves#169, added support for codeCoverageEnabled flag in target schemes.
* #170@yonaskolb code review fix and docs update.
* More #170@yonaskolb code review fix.
* Using gatherCoverageData instead of codeCoverageEnabled naming, thanks @kastiglione.
* Now using xcproj 1.5.0
* Another #170@yonaskolb code review fix.
