Kirill Kounik <[email protected]> writes: > I am interested in multi-gigabyte original shared libraries. Thanks for the > pointer, that's exactly what I need as I overlooked this location > originally! > > Followup question: can xwalk build system be configured to build both 'arm' > and 'x86' distributions at the same time. Something like having string > > { 'GYP_DEFINES': 'OS=android target_arch=arm,ia32', } > > in "chromium.gyp_env" file? The example above doesn't work.
Unfortunately, it's not possible to do that, it's a limitation we inherit from Chromium itself. You really need to have to separate and independent builds when you target different architectures. > W/ Best Regards, > Kirill > > On Tue, Mar 29, 2016 at 1:39 PM, Raphael Kubo da Costa < > [email protected]> wrote: > >> Kirill Kounik <[email protected]> writes: >> >> > Hi, >> > >> > I've successfully build Crosswalk branch crosswalk-17. My goal is to get >> > debug symbols for libxwalkcore.so library. However library located at >> > 'out/Debug/xwalk_core_library/libs/armeabi-v7a/libxwalkcore.so' doesn't >> > contain debug symbols. >> > >> > What arguments should I pass to the build command or wht should I do to >> get >> > library built with the debug symbols? >> >> The libraries are stripped automatically as part of the build, but you >> should still be able to get proper backtraces and symbolize them. >> >> Do the instructions in >> https://www.chromium.org/developers/how-tos/debugging-on-android help >> you or do you really need the multi-gigabyte original shared libraries >> (which are available in out/Debug/lib)? >> _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
