You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will be important functionality, and I think we'll want a swift-evolution proposal for the semantics around this and in particular the effect on the `PackageDescription` API.
Additional Detail from JIRA
md5: d248170c0dac973ed70706078d031c1c
Issue Description:
It'd be nice to be able to define targets that are built only in test/dev environments, but not as part of a package.
Given a package that specifies test targets (note: actual API is TBD, but here's an example)
When I specify the package as a dependency, then ExamplePkgTarget should be built, and ExampleTestTarget should not be built
When the Example Package is the root package, then both ExamplePkgTarget and ExampleTestTarget should be built.
When a user specifies no test targets, assume (as we do now) that all targets will be built upon distribution.
Test targets should be allowed to link against testDependencies, while "normal" targets should not.
The text was updated successfully, but these errors were encountered: