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
A package's declared swift tools version determines not only the API that is available to the package manifest, but also the semantics used for the target at build time. This can include how a Clang target's headers are represented in an automatically generated module map, etc.
Currently, targets in the SwiftPM package model don't record the declared tools version of the package manifest from where they came. This tracks the work of plumbing that information through so that it is available to the build plan and libSwiftPM clients.
The text was updated successfully, but these errors were encountered:
@aciidb0mb3r pointed out that there is API to get from the target to the package, from where we can then get the tools version. So additional API is not needed.
Additional Detail from JIRA
md5: 3f77995b30f6cf5878d066d7a59a6f6d
Issue Description:
A package's declared swift tools version determines not only the API that is available to the package manifest, but also the semantics used for the target at build time. This can include how a Clang target's headers are represented in an automatically generated module map, etc.
Currently, targets in the SwiftPM package model don't record the declared tools version of the package manifest from where they came. This tracks the work of plumbing that information through so that it is available to the build plan and libSwiftPM clients.
The text was updated successfully, but these errors were encountered: