Fix Swift Package Manager support #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Package.swift MUST specify a version according to https://developer.apple.com/documentation/xcode/creating_a_standalone_swift_package_with_xcode. Failure to do so causes Swift Package Manager to assume the version is 3.1.0, which is no longer supported.
This is necessary for Swift Package Manager to work.
Saklad5
changed the title
Unless a custom path is specified (which seems unnecessary in this instance), files in the target should be in a subfolder of Sources.
This is necessary for actually importing the module.
This is necessary for package testing to work. Similar to the main target, it needs to be in a special subfolder of Tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Package.swift MUST specify a version according to https://developer.apple.com/documentation/xcode/creating_a_standalone_swift_package_with_xcode.
Failure to do so causes Swift Package Manager to assume the version is 3.1.0, which is no longer supported.