-
Notifications
You must be signed in to change notification settings - Fork 31
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
cargo-apk compilation problem #23
Comments
@hanxiaohuivc In my case, I had to rename the name of the library. |
It does since #26, but that hasn't been released yet because this crate is officially deprecated in favour of Perhaps I'll do one more final release with the last few contributions, and a clear marker at the top of the The error @hanxiaohuivc is facing sounds like they have not set their |
I have the same problem since I move my main.rs in examples directory. |
Thanks, it works perfectly |
Too bad. Now I cannot launch my example compiled for linux.
Any Idea ? |
Something realy ugly is that with ["bin"] if an old file aarch64 libskybox1.so was previously successfully built, then this old file is packaged in the apk and the build is successfull. |
Agreed, it's ugly and unfortunate but not something we can very easily work around. Having two examples is likely your best bet for the time being. |
I've found the solution. I create a symbolic link of the example, set te example crate-type to "cdylib" and run the link for PC tests. it works well with VS code and launch.json. |
Such tricks also exist with |
cargo-apk compilation problem
Excuse me, when I compile using the "cargo apk build" command on both windows and linux, the following error occurs: Error: Path
"/home/develop/cargo-apk/target/aarch64-linux-android/debug/libndk_build.so"
doesn't exist.What is the cause of this? How to compile it correctly?
Thanks.
The text was updated successfully, but these errors were encountered: