We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Linux build currently fails with various errors of the form
.../SQLite.swift/Sources/SQLite/Core/Connection.swift:32:8: error: no such module 'CSQLite' import CSQLite
Perhaps a GitHub Actions CI pipeline could be added to avoid regressing on such things?
The text was updated successfully, but these errors were encountered:
Hm, it seems as if pinning the dependency version of SQLite.swift in the package manifest is an issue. Declaring
SQLite.swift
.package(url: "https://github.com/stephencelis/SQLite.swift", .branch("master"))
correctly yields
. └── SQLite.swift<https://github.com/stephencelis/SQLite.swift@unspecified> └── CSQLite<https://github.com/stephencelis/CSQLite.git@0.0.3>
whereas declaring
.package(url: "https://github.com/stephencelis/SQLite.swift", from: "0.13.0")
yields a dependency tree without CSQLite
CSQLite
. └── SQLite.swift<https://github.com/stephencelis/SQLite.swift@0.13.0>
Perhaps this is a bug in the Swift Package Manager? (I am running Swift 5.4.2 on Linux)
Sorry, something went wrong.
this is a bug with the released version, and was fixed in #1077
Ah okay, thanks! 👍
No branches or pull requests
The Linux build currently fails with various errors of the form
Perhaps a GitHub Actions CI pipeline could be added to avoid regressing on such things?
The text was updated successfully, but these errors were encountered: