kawari/build.rs

fn main() {
    println!("cargo:rustc-link-search=./oodle");
}
Clarify Oodle instructions, link against "oodle" directory While you can just drop the Oodle static library into /usr, I'm not a big fan of doing it, especially when the binary didn't come from my machine or package manager. You can set a RUSTFLAGS environment variable or cargo config file to specify a link path, but having the build script search there for you is easier. The docs now specify which variant of Oodle is required, since there are multiple. It also specifically mentions the static library, because I had some weird issues leaving the dynamic library in that folder, where the executables wouldn't start unless it could dynamically load the .so. 2025-03-17 14:08:51 -04:00			`fn main() {`
			`println!("cargo:rustc-link-search=./oodle");`
			`}`