mirror of
https://github.com/isar/rusqlite.git
synced 2025-02-01 05:20:51 +08:00
fe80b51e89
This is useful because currently, when using `rusqlite` in a Cargo workspace with one crate that uses `sqlcipher` and another that uses `bundled`, a build error will be triggered by an unqualified `cargo build` (as cargo will use the union of all features enabled by crates in the workspace). Instead of panicing, this just emits a warning, before (mostly) ignoring that the `bundled` feature was specified. Note: in this configuration, we still use our bundled bindings, to avoid changing `rusqlite` to handle this edge case (hence 'mostly').