Split MacOS binaries into amd64 and x64 versions to allow each to be shipped separately (feature request)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, macos
- Domain
- build-system, release
Research direction
The issue names the DuckDB JAR and the libduckdb_java.so_osx_universal native artifact; start by locating the JAR/native-library packaging and macOS build entry points. Done means arm64 and x64 macOS binaries are emitted as separate files and the JAR can include only the selected architecture.
Written by the indexing model from the issue text.
Description
The DuckDB JAR file is currently 73.3MB, which is a bit large for embedding into downloadable applications. Most of this comes from the four platform-dependent binaries inside:
- libduckdb_java.so_linux_amd64 (54.6MB)
- libduckdb_java.so_linux_arm64 (50.9MB)
- libduckdb_java.so_osx_universal (98.6MB)
- libduckdb_java.so_windows_amd64 (28.3MB)
It's easy enough to delete all of these but the one relevant to the architecture actually targeted in the bundle. But for the MacOS case, the arm64 and x64 binaries are combined into a single large "universal" executable. It would be helpful if the architectures were kept in separate files, so that only the relevant one could be included.
- Dominant language
- C++
- Stars
- 127
- Forks
- 80
- Avg merge
- 13h 41m
- Merged PRs (30d)
- 44
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-java
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
duckdb/duckdb-java#832 · 2 comments ·
-
Native SIGSEGV in DuckDB JDBC when repeatedly executing queries with window functions and LIMIT 0 Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-java#871 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
duckdb/duckdb-java#872 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
duckdb/duckdb-java#837 ·
-
executeBatch()` on a prepared INSERT runs s are ~1–2 orders of magnitude slower than the Appender Open
Difficulty 5/5 Over a week Newbie friendliness 42/100
duckdb/duckdb-java#815 · 1 comment ·
All issues in duckdb/duckdb-java
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·