This repo requires the duckdb/bundled feature and thus building libduckdb-sys from source.
Would it be possible to handle this the same way it is handled in the sqlite case?
Having a duckdb feature that dynamically links against and existing duckdb library and a duckdb-bundled feature that builds from source.
The underlying spiceai_duckdb_fork would allow for this in its features.
Instead of changing the duckdb feature one could also just introduce a duckdb-system feature would enable the dynamic linking.
This repo requires the duckdb/bundled feature and thus building libduckdb-sys from source.
Would it be possible to handle this the same way it is handled in the sqlite case?
Having a
duckdbfeature that dynamically links against and existing duckdb library and aduckdb-bundledfeature that builds from source.The underlying
spiceai_duckdb_forkwould allow for this in its features.Instead of changing the
duckdbfeature one could also just introduce aduckdb-systemfeature would enable the dynamic linking.