Alexander Biemann <[email protected]> writes: > We tried the build ninja -C out/Release xwalk_app_template_apk > and I used the resulting jar xwalk_core_java.jar in the Android app > > However, this resulted in an Assert()
[...] > It seems that findEmbeddedCore() returns false This is something we've been experiencing in our experimental branch with Chromium 44, but it shouldn't be the case with master. > We then tried to build with ninja -C out/Release xwalk_runtime_lib_apk > However, this resulted in a compile failure (we are configured to > build for "arm") [...] > The branch we have checked out is "main". > > What is the build statement to get an equivalent jar to replace > 'org.xwalk:xwalk_core_library:13.42.319.11' ? > Then finally, we can modify the code, rebuild, and test. Let me try to answer everything at once: I think by "main" you meant "master". That currently means Crosswalk 15. So the first thing you need to do to build Crosswalk 13 is check out the crosswalk-13 branch and then run gclient sync (possibly setting managed to False in .gclient first). Though if your intention is to send a patch on GitHub, sending it against master is a better idea. The target that we normally build is "xwalk_builder" as it builds all the APKs, including some test ones. You can try going for that and see if it solves your problems (the build ones, at least). _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
