CC'ing the crosswalk-help mailing list. This is a general question and the answer can possibly benefit other people too.
rahul pal <[email protected]> writes: > All, > Am able to get the problem resolved. > > Now only issue am facing is: > Another observation was that we were hoping to build the AAR file that has > .so for both arm and intel, how to ensure that. As when we configure GYP as > following ones , we do not get intel specific .so files generated in the > aar. None of following work to generate both. At a time only one .so gets > generated. > echo "{ 'GYP_DEFINES': 'OS=android', }" > chromium.gyp_env OR > echo "{ 'GYP_DEFINES': 'OS=android target_arch=arm', }" > chromium.gyp_env > OR > echo "{ 'GYP_DEFINES': 'OS=android target_arch=ia32', }" > chromium.gyp_env > ninja -j8 -C out/Release xwalk_core_library_aar To generate shared libraries for different architectures, you need separate builds. `target_arch=arm` will generate ARM shared libraries, just like `target_arch=ia32` will generate 32-bits X86 shared libraries. It is up to you to later combine them together (which is what we do in our releases, for example). > Kindly guide with suggestion. > > thanks > > On Fri, Jun 12, 2015 at 1:03 PM, rahul pal <[email protected]> wrote: > >> Thanks for the response Hengzhi. >> >> Might not be possible for me to make that chane in my App manifest, as we >> are using MultiDexSupport in our Application. >> >> Will there be any option to not do that in future releases of Xwalk >> >> thanks >> >> >> On Thu, Jun 11, 2015 at 6:39 PM, Wu, HengzhiX <[email protected]> >> wrote: >> >>> Hi, rahul pal >>> >>> >>> >>> This issue was introduced by >>> https://github.com/crosswalk-project/crosswalk/pull/3080, the >>> application context should be passed to follow the upstream’s change. >>> >>> In this PR, I am missing the judgment for the instance of >>> XWalkApplication, sorry for the inconvenience. >>> >>> Please add android:name=”org.xwalk.core.XWalkApplication” to >>> <application> element in AndroidManifest.xml >>> >>> Thanks. >>> >>> >>> >>> BRs, >>> >>> Hengzhi Wu >>> >>> >>> >>> *From:* rahul pal [mailto:[email protected]] >>> *Sent:* Friday, June 12, 2015 6:56 AM >>> *To:* Sun, Lin; Wu, HengzhiX; Fu, Junwei; Kubo Da Costa, Raphael >>> *Subject:* Re: XWALK-4380 : Reg. building Crosswalk on Android >>> >>> >>> >>> What is the exact GYP/ninja set of build commands that Xwalk uses for >>> creating its Release AARs for Android. >>> >>> As the instructions for building , seems to be lacking some details. >>> >>> >>> >>> On Thu, Jun 11, 2015 at 3:11 AM, rahul pal <[email protected]> wrote: >>> >>> hi , >>> >>> Thanks a lot for all your contributions to the Xwalk project. >>> >>> >>> >>> We have been trying to build Xwalk for Android client, and seeing crash >>> in Xwalk lib. with the build target aar, when we try to pull in our App. >>> The same App works fine with the Standard Xwalk Release aar. >>> >>> >>> >>> Have raised a JIRA https://crosswalk-project.org/jira/browse/XWALK-4380, >>> with further details and info. >>> >>> >>> >>> Basically we want to bring our observation to your notice, and ensure >>> that we are not missing any critical step in building xwalk, or in using >>> the generated AAR. >>> >>> >>> >>> Another observation was that we were hoping to build the AAR file that >>> has .so for both arm and intel, how to ensure that. As when we configure >>> GYP as following ones , we do not get intel specific .so files generated in >>> the aar. None of following work to generate both. At a time only one .so >>> gets generated. >>> >>> echo "{ 'GYP_DEFINES': 'OS=android', }" > chromium.gyp_env OR >>> >>> echo "{ 'GYP_DEFINES': 'OS=android target_arch=arm', }" > >>> chromium.gyp_env OR >>> >>> echo "{ 'GYP_DEFINES': 'OS=android target_arch=ia32', }" > >>> chromium.gyp_env >>> >>> >>> >>> >>> >>> thanks for your time and help, would help us if you can have a look at >>> this. >>> >>> >>> >>> regards >>> >>> Rahul Pal >>> >>> >>> >>> >>> >>> >>> >> >> _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
