rahul pal <[email protected]> writes: > hi Raphael, > Can you list the exact steps: > 1) Do you delete the out folder completely before building for the new arch, > as it wont build the new .so for me. Would following work: > Building for 32bit x86 > export GYP_GENERATORS='ninja' > export XWALK_OS_ANDROID=1 > echo "{ 'GYP_DEFINES': 'OS=android target_arch=ia32', }" > > chromium.gyp_env > cat chromium.gyp_env > cd src/ > . ./xwalk/build/android/envsetup.sh > python xwalk/gyp_xwalk > ninja -j8 -C out/Release xwalk_core_library_aar > > rm -rf out > > Building for ARM > export GYP_GENERATORS='ninja' > export XWALK_OS_ANDROID=1 > echo "{ 'GYP_DEFINES': 'OS=android target_arch=arm', }" > > chromium.gyp_env > cat chromium.gyp_env > cd src/ > . ./xwalk/build/android/envsetup.sh > python xwalk/gyp_xwalk > ninja -j8 -C out/Release xwalk_core_library_aar > > 2) How do you combine the two .so once you get it. Do you just copy the new > arch files into > the jni folder.
Each build is done on a separate machine, but the effect is the same as starting from scratch in a new out/ directory, so the steps you have described are OK (it's not necessary to call `cat` or source envsetup.sh though). AAR files are just zip files; given the only difference between the ARM and x86 AAR files are the different shared libraries, you can use something like zipmerge(1) or anything that merges zip files (or even extract everything into some directory and then create one new zip file) to build one final, multi-architecture AAR archive. _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
