Apps using `winsqlite3` feature no longer builds about rusqlite HOT 5 OPEN

#1270 (comment)

the compiled version of SQLite inside of Windows is only meant to be used by projects that are bundled as part of the Windows operating system ( microsoft/win32metadata#824 (comment)), not non-Microsoft projects.

from rusqlite.

@gwenn

Thanks for pointing it out. CMIIW, I think the statement you are quoting does not come from an official source or documentation that Microsoft claims?

Regarding the comment microsoft/win32metadata#824 (comment), maybe someone misinterprets it here?

Windows ships a compiled version of SQLite in System32/winsqlite3.dll that certain OS projects depend on. If you want to use this version to reduce your overall binary size, you can link against this version instead of compiling it directly into your own project.
I don't recommend that for non-OS projects, but that's where it comes from. @jonwis may have some guidance here.

AFAIK it just looks like some kind of personal preference, instead of an official announcement of the direction that winsqlite3 in Windows is going to follow. link against this version instead of compiling it directly into your own project is still an option.

Well I understand that it might be a maintenance burden given few people use it. Now that winsqlite is already implemented and shipped in stable releases, I would suggest still keeping the option to use winsqlite and remove only the tests, and then let those who need it to test it out.

from rusqlite.

For your reference, winsqlite3 is also available as a provider of the .NET library Microsoft.Data.Sqlite.

https://learn.microsoft.com/en-us/dotnet/standard/data/sqlite/custom-versions?tabs=netcore-cli

from rusqlite.

@davidbarsky, @thomcc
Could you please advise ?

from rusqlite.

@davidbarsky, @thomcc

Could you please advise ?

I can't reasonably advise, but the fact that feature flag has bitten me when vendoring crates into a monorepo will remain a risk if it returns.

As a person consuming this library (but not necessarily using it), the RUSTFLAGS approach I mentioned in the original issue won't cause me or my employer much difficulty or risk. That being said, I think the .NET team will have substantially more viability into what version of sqlite version will be bundled into Windows than me, so I'm not exactly qualified to opine.

from rusqlite.