Bundling third_party and other dependencies needed in libduckdb_static.a #9475
Labels
Comments
1 task
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
carlopi
added a commit
to carlopi/duckdb
that referenced
this issue
Feb 7, 2024
make bundle-library can be used by third party developers that want to statically link against duckdb library to generate a single static library comprised of all statically built extensions and all necessary third party libraries Solves (to some degree) duckdb#9475 and issue encountered in the go-duckdb API while bundling extensions
|
#10507 partially address this problem, idea is allowing developers to run make bundle library to have a static library bundle all third party AND all build extensions in a single bundle. Currently this is not going to be packaged as part of releases on GitHub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happens?
libduckdb_static.ais not part of the release but it's not usable because it doesn't include the various dependencies needed (for example the ones in thethird_partyfolder).For anyone writing a program to access duckdb programmatically, currently they cannot statically link to the provided
libduckdb_static.abecause of those missing references.I first opened a discussion #9451 and was told to file this issue.
To Reproduce
Write a program using the C api such as
db_connect,db_disconnect, and etc and try to link the program using the providedlibduckdb_static.a.#9451
OS:
Ubuntu 22.04 LTS
DuckDB Version:
0.9.1
DuckDB Client:
C
Full Name:
Ed Yu
Affiliation:
Beachglass Labs
Have you tried this on the latest
mainbranch?I have tested with a main build
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: