With Xcode 10 dependent targets won't start compiling until compilation and all run scripts are done for the target. This means that your run script should run before Copy Files (and Copy Resources, etc.) phases unless it needs to run later, to allow dependent targets to compile faster.
Allows for choice on if `copy-frameworks` or an `Embed Frameworks` build phase should be used to embed Carthage framworks. Defaults to `true` for macOS targets to match current behavior.
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.
This adds a new attribute to Dependency that allows consumers to choose
to not link a dependency. This is useful for if you have this dependency
tree with static libraries:
App -> A -> Shared
App -> B -> Shared
Where A and B both share a static library dependency, that is finally
linked into App. If Shared is added to the link phase of A and B, you
end up with duplicate symbols during the link phase. With this change
consumers could set link: False on A and B's dependency on Shared, this
way Shared will get build before A and B, but not linked.