Fix macOS Build

b3ll · Oct 12, 2024 · c460622 · c460622
1 parent c8611d9
commit c460622
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 1 deletion.
diff --git a/Package.swift b/Package.swift
@@ -8,7 +8,7 @@ let package = Package(
     platforms: [
         .iOS(.v13),
         .tvOS(.v13),
-        .macOS(.v10_14),
+        .macOS(.v10_15),
         .visionOS(.v1)
     ],
     products: [

diff --git a/Sources/Motion/Utilities/AnimationDriver.swift b/Sources/Motion/Utilities/AnimationDriver.swift
@@ -136,6 +136,7 @@ import Cocoa
 
 typealias SystemAnimationDriver = CoreVideoDriver
 
+@MainActor
 final class CoreVideoDriver: AnimationDriver {
 
     private var displaylink: CVDisplayLink!

diff --git a/Sources/Motion/Utilities/AnimationEnvironmentProxy.swift b/Sources/Motion/Utilities/AnimationEnvironmentProxy.swift
@@ -31,6 +31,7 @@ import AppKit
  it wouldn't be safe to start the animation in `viewDidLoad`. Generally, a safe place to start an animation tied to a view or view controller
  is any time after `viewDidAppear` and before `viewDidDisappear`, which is when the view is in a window, and its window is on screen.
  */
+@MainActor
 public protocol AnimationEnvironmentProxy: AnimationEnvironment {
     var proxiedAnimationEnvironment: AnimationEnvironment { get }
 }

diff --git a/Sources/Motion/Utilities/NSScreen+AnimationEnvironment.swift b/Sources/Motion/Utilities/NSScreen+AnimationEnvironment.swift
@@ -10,6 +10,7 @@ public final class DefaultAnimationEnvironment: NSScreen {
     }
 }
 
+@MainActor
 extension NSScreen: AnimationEnvironment {
     private var environmentStorage: AnimationEnvironmentStorage { AnimationEnvironmentStorage.shared }
 
@@ -35,6 +36,7 @@ private extension NSDeviceDescriptionKey {
     static let screenNumber = NSDeviceDescriptionKey("NSScreenNumber")
 }
 
+@MainActor
 private final class AnimationEnvironmentStorage {
     static let shared = AnimationEnvironmentStorage()