Fixes#193
This addresses the issue that it was impossible to test targets if
custom scheme was used by providing array of testables to `Test` action.
Now it should be possible using the following syntax:
```yaml
STCore:
build:
targets:
- target: STCore
buildTypes: all
test:
testables: [STCoreTests]
config: Staging-Debug
```
Note that original example in #193 has to be modified for this change
as it causes a confusion in Xcode: if we have 2 targets `STCore` and
`STCoreTests`, if `STCoreTests` is also added as testable Xcode
duplicates test target in build actions (i.e. `STCore`, `STCoreTests`,
`STCoreTests` are shown).
It's not enough just set command line arguments - there is a separate
flag in scheme, which allows them to overwrite default launch arguments.
Now that flag is automatically set if there are any args provided.
Fixes#198
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.
Yonas Kolb
Valerii Hiora
Yonas Kolb
Brandon Kase
Rahul Malik
Alex Rupérez