We currently redistribute SQLite, but only for UWP and Windows. On OSX and Linux, we assume it is already installed globally.
Ideally, we'd like to get out of the business of redistributing SQLite, and either (1) do nothing (not the best experience on Windows), or (2) depend on an official, SQLite-owned NuGet package.
We tried, with the SQLite team, to produce a NuGet 3 package--sqlite--for redistributing it, but there was no way do differentiate between a native library that can only run inside of an App container (the WinRT/UWP ones) and the other ones (Win32). (See this conversation.) NuGet 3 also fails to handle Full .NET, AnyCPU apps. (See NuGet/Home#904.) We currently do some fancy MSBuild magic in our package to workaround these. We should work with the NuGet and .NET Core teams to figure out a best practice to use in this situation. Then try again with the SQLite team to produce a package that works with Full .NET, UWP, and .NET Core.
cc @mistachkin, @ericsink, @timheuer