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
When making port packages, I usually start off by making the vendored code accessible (e.g., via a submodule) and then symlinking in the code to match SwiftPM’s expected structure.
This works well, but one confusing situation is when you symlink an entire subdirectory, SwiftPM won’t traverse it looking for sources to build. This should probably be a warning.
Additional Detail from JIRA
md5: 67ac10f4be9c44cdf18ae1596b53ef47
duplicates:
Issue Description:
Filed on behalf of @ddunbar:
When making port packages, I usually start off by making the vendored code accessible (e.g., via a submodule) and then symlinking in the code to match SwiftPM’s expected structure.
This works well, but one confusing situation is when you symlink an entire subdirectory, SwiftPM won’t traverse it looking for sources to build. This should probably be a warning.
Something like:
–
The text was updated successfully, but these errors were encountered: