Repository navigation
Linux ARM64 build: hardcoded x86_64 resource path blocks aarch64 builds #185
paulpeek77
started this conversation in
Ideas
Replies: 1 comment 3 replies
|
tauri has automatic config files per os but you can select a cpu specific overlay explicitly with |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I did a thing. What do you think?
Background
Successfully built v3.0.6 on aarch64 Linux (ThinkPad X13s, Snapdragon 8cx Gen 3, Fedora Rawhide). Full details in PR #184 (lockfile refresh for OpenSSL 4.0).
Hit a blocker during build:
src-tauri/tauri.linux.conf.jsonhard-codes the resource glob as:This fails on ARM64 because that directory doesn't exist.
My Workaround
Temporarily swapped to resources/llama/aarch64-unknown-linux-gnu/* and copied .so libraries from llama.cpp source. But this just trades one hardcoded arch for another — breaks x86_64 users.
Questions for Maintenance
What shape would you accept for a proper fix? Options I can think of:
I'm happy to contribute a PR once we agree on the approach. Also happy to test an aarch64 CI lane if one gets spun up.
For reference: [PR #184] resolves the OpenSSL 4.0 lockfile issue.
All reactions