New release of libsql on crates.io?

[awakecoding]

The current libsql release on crates.io (0.6.0) is 5 months old, and we're currently pinning a commit id which fixes the build on Windows. Would it be possible to publish a new release of libsql soon such that the latest published version builds on Windows out of the box?

Thanks!

[penberg]

@awakecoding I have now published libsql 0.9.1 on crates.io.

[kunjee17]

@awakecoding have you checked this one. Because I m getting same issue one "0.9.2" version.

22:05:33 [cargo] error: failed to run custom build command for `libsql-ffi v0.9.2`
22:05:33 [cargo] Caused by:
22:05:33 [cargo]   process didn't exit successfully: `...\target\debug\build\libsql-ffi-2ab13c57ae04c82e\build-script-build` (exit code: 101)
22:05:33 [cargo]   --- stdout
22:05:33 [cargo]   cargo:rerun-if-changed=bundled/src/sqlite3.c
22:05:33 [cargo]   --- stderr
22:05:33 [cargo]   thread 'main' panicked at ...\libsql-ffi-0.9.2\build.rs:44:44:
22:05:33 [cargo]   called `Result::unwrap()` on an `Err` value: Error { kind: NotFound, message: "program not found" }
22:05:33 [cargo]   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
22:05:33 [cargo] warning: build failed, waiting for other jobs to finish...
22:05:33 [dev] Build failed: Other(Cargo build failed, signaled by the compiler. Toggle tracing mode (press `t`) for more information.)

[allan2]

Windows builds are still not working. The problem and the fix are described in my PR #2005.

[kunjee17]

@allan2 basically I wanted this to for desktop application so there is not way out else could have run from WSL. Is there any ETA on this or it is law level issue ?

[awakecoding]

@penberg would it be possible to at least ensure continued support for Windows in the CI? simple build breakage like this are quite a problem