HACK: hardcode toolchain location

We should figure out the proper way to identify the toolchain
installation rather than assuming the install location.

Author: compnerd

Source/SourceKittenFramework/Module.swift

@@ -92,7 +92,7 @@ public struct Module {
      */
     public init?(spmArguments: [String], spmName: String? = nil, inPath path: String = FileManager.default.currentDirectoryPath) {
         fputs("Running swift build\n", stderr)
-        let buildResults = Exec.run("/usr/bin/env", ["swift", "build"] + spmArguments, currentDirectory: path, stderr: .merge)
+        let buildResults = Exec.run("C:\\Library\\Developer\\Toolchains\\unknown-Asserts-development.xctoolchain\\usr\\bin\\swift.exe", ["build"] + spmArguments, currentDirectory: path, stderr: .merge)
         guard buildResults.terminationStatus == 0 else {
             let file = URL(fileURLWithPath: NSTemporaryDirectory()).appendingPathComponent("swift-build-\(UUID().uuidString).log")
             _ = try? buildResults.data.write(to: file)

Source/SourceKittenFramework/library_wrapper.swift

@@ -158,6 +158,7 @@ let toolchainLoader = Loader(searchPaths: [
 // MARK: - Windows
 
 let toolchainLoader = Loader(searchPaths: [
+    "C:\\Library\\Developer\\Toolchains\\unknown-Asserts-development.xctoolchain\\usr\\bin",
 ].compactMap {
     FileManager.default.fileExists(atPath: $0) ? $0 : nil
 })