Android Qt 5.8 RC x86: cannot run x86 app on x86 emulator
-
I have just installed the latest 5.8 RC snapshot, built the app no problem (I only built ARM previously), but I can't run it in an x86 (not x86_64) emulator:
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/org.my.App-1/lib/x86/libApp.so" has unexpected e_machine: 40
Is it a known problem? Do I need to reconfigure the project for x86 somehow?
-
I have just installed the latest 5.8 RC snapshot, built the app no problem (I only built ARM previously), but I can't run it in an x86 (not x86_64) emulator:
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/org.my.App-1/lib/x86/libApp.so" has unexpected e_machine: 40
Is it a known problem? Do I need to reconfigure the project for x86 somehow?
@Violet-Giraffe
about what lib are we talking here? Is it a custom lib of yours?
Maybe rerun qmake and perfom a full rebuild.This lib is missing in your apk it seems. Have you added it to your android folder (qmake/QtCreator)?
-
@Violet-Giraffe
about what lib are we talking here? Is it a custom lib of yours?
Maybe rerun qmake and perfom a full rebuild.This lib is missing in your apk it seems. Have you added it to your android folder (qmake/QtCreator)?
@raven-worx
I have run and re-run qmake, built and re-built the project many times.What I didn't do was delete the bin/ and build/ folders and then rebuild. My bad. That solved the problem - now the .so is loaded fine and I get the same Qt-induced OpenGL errors that I do in an ARM project.
-
@raven-worx
I have run and re-run qmake, built and re-built the project many times.What I didn't do was delete the bin/ and build/ folders and then rebuild. My bad. That solved the problem - now the .so is loaded fine and I get the same Qt-induced OpenGL errors that I do in an ARM project.
@Violet-Giraffe
this should happen implicitly when you are perfoming therebuild
step (i was talking about) -
@Violet-Giraffe
this should happen implicitly when you are perfoming therebuild
step (i was talking about)@raven-worx
It should, but obviously something wasn't re-generated properly.