Hi! It seems that answer wasn't addressed to me. My original question was:
I try to embedding crosswalk webview into my android application. I followed the instructions from here https://crosswalk-project.org/documentation/embedding_crosswalk.html 1) crosswalk project (crosswalk-webview-13.42.319.11-arm) was downloaded and imported into my eclipse workspace. 2) crosswalk project was marked as library in project properties and was added as reference in my android project properties. Then I tried to build my project and as result I received error: The container 'Android Dependencies' references non existing library '/Users/xxx/igarant/AndroidGarant/crosswalk-webview-13.42.319.11-arm/bin/crosswalk-webview-13.42.319.11-arm.jar' So, there is no jar file in bin folder. I hope on your help, thanks.. Best regards, Matveev Sergey. 2015-06-16 12:47 GMT+04:00 Raphael Kubo da Costa < [email protected]>: > 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 >
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
