-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build Carthage with SPM in Swift 5 #2752
Comments
Hi! This issue already fixed on this commit. It will be fixed on next version. |
0.33.0 is out, so this should be fixed! |
I found an another issue. Since 0.33.0, SwiftPM was added as dependencies. It seems to be SwiftPM's bug rather than Carthage's issue. SwiftPM couldn't treat non semver tag well. (lilke You can avoid this problem using I'll make an issue on Swift Jira. let package = Package(
name: "CarthageSwiftPM",
products: [
// Products define the executables and libraries produced by a package, and make them visible to other packages.
.library(
name: "CarthageSwiftPM",
targets: ["CarthageSwiftPM"]),
],
dependencies: [
// Dependencies declare other packages that this package depends on.
// It works
.package(url: "https://github.com/Carthage/Carthage", .revision("c8ac06e106b6b61f907918bfb2b7a5c432de4678")),
// Don't work
// .package(url: "https://github.com/Carthage/Carthage", .exact("0.33.0")),
// .package(url: "https://github.com/Carthage/Carthage", .upToNextMinor(from: "0.33.0")),
],
targets: [
// Targets are the basic building blocks of a package. A target can define a module or a test suite.
// Targets can depend on other targets in this package, and on products in packages which this package depends on.
.target(
name: "CarthageSwiftPM",
dependencies: ["Carthage"]),
.testTarget(
name: "CarthageSwiftPMTests",
dependencies: ["CarthageSwiftPM"]),
]
)
|
Carthage 0.32.0 isn't building with Swift 5 via the Swift package manager. This affects Mint installations.
Doing so leads to the error:
Master seems to build ok (just with a lot of warnings), so I guess a new release will fix it. Feel free to close this.
The text was updated successfully, but these errors were encountered: