Files
Lumotia/crates/transcription/Cargo.toml
Cursor Agent 1bb39699f5 feat(A.1 #6): fail Windows build when tokenizers enters the dep graph
Adds a build.rs guard that parses Cargo.lock and panics on Windows
if the tokenizers crate ever appears in the workspace dependency
tree, mirroring the MSVC C-runtime conflict that broke Whispering
v7.11.0 when they linked whisper-rs-sys + tokenizers in the same
binary.

On non-Windows hosts the guard downgrades to a cargo:warning so
cross-compilation or CI from Linux surfaces the issue before a
Windows build attempt actually panics.

No tokenizers crate is in the tree today; the guard is preemptive.
If we ever legitimately need HF tokenizers on Windows, the escape
hatch is an out-of-process sidecar (separate CRT).

Co-authored-by: jars <jakejars@users.noreply.github.com>
2026-04-21 15:54:15 +01:00

32 lines
926 B
TOML

[package]
name = "kon-transcription"
version = "0.1.0"
edition = "2021"
description = "Speech-to-text engine wrappers, model management, and inference concurrency for Kon"
build = "build.rs"
[dependencies]
kon-core = { path = "../core" }
# Parakeet via ONNX. Whisper is handled directly via whisper-rs below.
transcribe-rs = { version = "0.3", default-features = false, features = ["onnx"] }
# Async runtime for spawn_blocking
tokio = { version = "1", features = ["rt", "sync"] }
# Model downloads
reqwest = { version = "0.12", features = ["stream"] }
futures-util = "0.3"
# Download integrity verification
sha2 = "0.10"
whisper-rs = { version = "0.16", default-features = false, features = ["vulkan"] }
# Direct whisper-rs backend (WhisperRsBackend): thread pool sizing + typed errors.
num_cpus = "1"
thiserror = "2"
# Structured logging at backend boundaries (observability for initial_prompt flow).
tracing = "0.1"