sqll-sys

Bindings to sqlite for sqll.

Note that the metadata field of this crate specified which version of sqlite is provided if the bundled feature is enabled, like +sqlite-3.51.1.

Features

• bundled - Use the bundled sqlite3 source code. If this feature is not enabled see the building with system dependencies section below.
• threadsafe - Build sqlite3 with threadsafe support. If this is not set then the bundled feature has to be set since we otherwise cannot control how sqlite is built.
• strict - Build sqlite3 with strict compiler flags enabled. This is only used when the bundled feature is enabled.

Building

When linking to a system sqlite library there is a minimum required version. This is specified in the sqlite3-version file and is checked at build time.

If the bundled feature is not set, this will attempt to find the native sqlite3 bindings using the following methods:

• Calling vcpkg, this can be disabled by setting the NO_VCPKG or SQLITE3_NO_VCPKG environment variables.
• Finding the library through pkg-config, this can be disabled by setting or by setting the SQLITE3_NO_PKG_CONFIG environment variables.

Building under WASM

If the target is is wasm, you can set the SDK_PATH_ENV to specify an SDK path to a particular compiler to use when building the wasm bindings. This is only supported when the bundled feature is enabled.

The following environment variables can be set to modify this behavior:

• SQLL_TARGET or TARGET to specify the build target. You probably want to set this to something like wasm32-wasi-unknown.
• SQLL_CLANG_PATH or CLANG_PATH to specify a custom path to a clang compiler installation.