-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] android build fails with libxml dependency #9560
Comments
Thought I'd try starting fresh. Recreated my projects src-tauri folder with |
Revisited this today with v2.0 beta 21. Same issue unfortunately. Started with an empty folder so none of my own code is involved, just the default tauri main.rs and lib.rs. |
beta 22 also has this same issue. When I built a non-mobile app, it doesn't have the libxml dependency: objdump -p yields:
So I suppose there's something specific about the android build that is pulling in libxml.so.2. The other thing is that after the first compile attempt for android, on subsequent attempts it starts on tauri-runtime-wry:
So it seems likely the link problem is happening when tauri-runtime-wry is compiled for android. |
Thought I'd update this. I'm not quite sure what the problem really was here but it is working now. Current version of tauri-zknotes is compiling and producing an apk, those interested in getting tauri working in a nixos env can check that out. There's also this, same flake but someone is documenting it for general use. |
Describe the bug
Trying to upgrade my app to beta-14;
cargo tauri android build --apk -t armv7
fails with libxml2.so.2 not found:Reproduction
bburdette/tauri-zknotes@d2afc79
build instructions in readme.
Expected behavior
expect it to link, and hopefully run on the android device.
Full
tauri info
outputStack trace
No response
Additional context
There is non-tauri rust code in this project, in the form of a library containing a web server. When I compile that on its own it doesn't contain libxml dependencies:
Here's the cargo build output:
The text was updated successfully, but these errors were encountered: