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
Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?
Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.
Description
Because swift build drops all modules into the same folder and passes that folder via a -I swiftc is able to see module that weren't explicitly depended upon in the Package.swift. Instead we can use -explicit-swift-module-map-file and tell the name and path to each module it should have visibility of.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version ; uname -a)
No response
The text was updated successfully, but these errors were encountered:
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?swift build
,swift test
,swift package
etc.Description
Because swift build drops all modules into the same folder and passes that folder via a
-I
swiftc is able to see module that weren't explicitly depended upon in the Package.swift. Instead we can use-explicit-swift-module-map-file
and tell the name and path to each module it should have visibility of.Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of
swift --version ; uname -a
)No response
The text was updated successfully, but these errors were encountered: