Not sure what's the exact upstream Chromium revision your code bases on, and it might be related to this: >From revision 252034, You don't need to append -target-arch to envsetup.sh. >Instead, you need to use gyp_chromium -Dtarget_arch=ia32 (not x86). If you >don't assign -Dtarget_arch, default arch is arm. >From revision 252166, if you pass -target-arch to envsetup.sh, it will report >an error.
So in your case, it fell back to arm build. And I guess you have a previous built x86 binary there, so the generated apk contains both your new arm binary and old x86 binary. The behavior of apk generation is a bit buggy for me. Regards, -Yang From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Hwang, Dongseong Sent: Tuesday, March 25, 2014 12:48 AM To: [email protected] Subject: [Crosswalk-dev] Question about Android build Hi, I found very interesting behavior. https://crosswalk-project.org/#contribute/building_crosswalk First of all, set up the Android build environment. If you are targeting ARM, pass arm instead of x86 below: . xwalk/build/android/envsetup.sh --target-arch=x86 When we build Crosswalk Android for x86 test device, we use x86 option. However, ninja uses arm toolchain, linux-x86_64/bin/arm-linux-androideabi-g++, although I use x86 options. Even odd, generated apk works well on x86 test device as well as Nexus 5. Could you explain this interesting behavior? My assumption is that x86 test device's jni linker can deal with arm shared object. Br, DS
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
