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 referencing WhisperKit from a SPM package as a dependency, it does not recognize the "v" prefixed version as a version string (for both from and exact). The error in Xcode is "Invalid semantic version string 'v0.9.0'".
It seems SPM doesn't recognize the "v" prefix from semantic versioning in this case.
Similarly, from the command line:
% swift build
error: 'mylibrary': invalid manifest (evaluation failed)
Invalid semantic version string 'v0.9.0'
error: 'mylibrary': invalid manifest (evaluation failed)
Invalid semantic version string 'v0.9.0'
The Package.swift file:
// swift-tools-version: 6.0
// The swift-tools-version declares the minimum version of Swift required to build this package.
import PackageDescription
letpackage=Package(
name:"MyLibrary",
products:[
// Products define the executables and libraries a package produces, making them visible to other packages.
.library(
name:"MyLibrary",
targets:["MyLibrary"]),],
dependencies:[.package(url:"https://github.com/argmaxinc/WhisperKit", from:"v0.9.0")],
targets:[
// Targets are the basic building blocks of a package, defining a module or a test suite.
// Targets can depend on other targets in this package and products from dependencies.
.target(
name:"MyLibrary",
dependencies:[.product(name:"WhisperKit",package:"WhisperKit")]),.testTarget(
name:"MyLibraryTests",
dependencies:["MyLibrary"]),])
The text was updated successfully, but these errors were encountered:
When referencing WhisperKit from a SPM package as a dependency, it does not recognize the "v" prefixed version as a version string (for both from and exact). The error in Xcode is "Invalid semantic version string 'v0.9.0'".
It seems SPM doesn't recognize the "v" prefix from semantic versioning in this case.
Similarly, from the command line:
The Package.swift file:
The text was updated successfully, but these errors were encountered: