I wiped out my Crosswalk folder, then re-sync'ed and successfully
completed the build process, or at least it appeared to complete.
The problem I now have is the 'make_apk.py' python script doesn't
complete because of missing files and folders.
This file is in "~/git/crosswalk/src/xwalk/app/tools/android/"
Some of these are just in the wrong place, which can be handled by soft
links:
For example the shared library 'libxwalkcore.so' is in:
$/git/crosswalk/src/out/Release/xwalk_core_shell_apk/libs/armeabi-v7a
instead of:
~/git/crosswalk/src/xwalk/app/tools/android/native_libs/armeabi-v7a/libs/armeabi-v7a
There's no 'app_src' folder at the same level as 'make_apk.py', but
that can be solved by a softlink to:
$/git/crosswalk/src/xwalk/app/android/app_templates
Some are just plain missing, so the folder "scripts/gyp" doesn't work,
but simply "gyp" does, because there is no 'scripts' folder at the same
level as 'make_apk.py'.
Even then some can't be resolved. For example there is no direct
equivalent to the 'jsapi' folder expected
'~/git/crosswalk/src/xwalk/app/tools/android/native_libs_res', even
though the individual JavaScript files exist, but are scattered under
subfolders of '$git/crosswalk/src/xwalk'
Unless there's a significant change to folder structure in crosswalk-7
(compared to crosswalk-6), I fear there's some step missed out
on the build process.
Note: I was able to build by HTML5 application under the standard
crosswalk-6 download (6.35.131.4). I'm trying to build a simple
extended version of crosswalk-7 to include the extended media formats
(ex: H-264) since my project requires these extended formats.
Roger
On 05/30/2014 04:46 PM, Alexis Menard wrote:
Hi,
So say you checkout the crosswalk-6 branch in the src/xwalk repository
then you need to come back to the root (your ~/git/crosswalk) to re
run gclient sync. This will refetch crosswalk-6 dependencies which
will allow the build to complete correctly.
trunk/master is crosswalk-7 with Chromium M36 (landed few days ago)
which slightly modified the way Android build. You need to add
xwalk_android_gyp -Dtarget_arch=ia32 -DOS=android . We need to fix the
documentation to reflect this. This is not relevant if you build
crosswalk-6, what's in the wiki is accurate.
Concerning your build errors I'm not very sure if they are relevant
since you had a frankenstein build. We do have buildbots so the build
is working fine. We need to see what's wrong with your setup but at
the moment you don't build/configure xwalk correctly.
Thanks for trying crosswalk.
On Fri, May 30, 2014 at 5:25 PM, Roger Stringer
<[email protected]> wrote:
Yes, I realized later the posted sequence wasn't quite right, but it didn't
appear to be the cause of my problems.
Yes, I'm reading the documentation very carefully and trying to follow it.
Right now I'm re-sync'ing and then rebuild without specifying a particular
Crosswalk version, but instead of getting (stable/beta) crosswalk-6 and
Chromium #35, it appears to be crosswalk-7 and Chromium #36 (36.0.1985.18).
Yes, I do need access to a fuller range of media type than is the default
and understand the constraints there. ex: H-264
I worry that my various build attempts have left my codebase in an
inconsistent state, and unless my current exercise succeeds, over the
weekend I'll delete the crosswalk codebase and start over, targeting
crosswalk-6
PS: See my subsequent post for other consequent build issues.
On 05/30/2014 03:57 PM, Alexis Menard wrote:
Hi,
On Fri, May 30, 2014 at 12:18 PM, Roger Stringer
<[email protected]> wrote:
~/git/crosswalk/src/xwalk$ GYP_DEFINES="OS=android" gclient runhooks
~/git/crosswalk/src/xwalk$ cd ..
~/git/crosswalk/src$ ninja -C out/Release xwalk
~/git/crosswalk/src$ ./xwalk/build/android/envsetup.sh
~/git/crosswalk/src$ export GYP_GENERATORS='ninja'
~/git/crosswalk/src$ python xwalk/gyp_xwalk -Dmediacodecs_EULA=1
-Dtarget_arch=arm
Traceback (most recent call last):
File "xwalk/gyp_xwalk", line 454, in <module>
vs2013_runtime_dll_dirs = vs_toolchain.DownloadVsToolchain()
AttributeError: 'module' object has no attribute 'DownloadVsToolchain'
========================
Platform: Ubuntu 14.04 in 64 bit mode
Settings:
XWALK_OS_ANDROID=1
XWALK_DIR=$HOME/git/crosswalk
ANDROID_HOME=$HOME/adt-bundle-linux-x86_64-20130917/sdk
========================
Commentary:
vs_toolchain.DownloadVsToolchain() is a function which returns a string
value, later tested to be non-empty
to determine where gyp_xwalk should call
vs_toolchain.CopyVsRuntimeDlls(...)
However the function is missing from my version of vs_toolchain.py
It looks like vs_toolchain.SetEnvironmentAndGetRuntimeDllDirs() returns
the
correct value, which appears
to be None on a Linux build. Not surprisingly, a function call
containing
"Dll" appears to be win32 specific. :-)
You're hitting the wrong code path because you're not following the
documentation.
https://crosswalk-project.org/#contribute/building_crosswalk
The list of commands you pasted are buggy and the order is incorrect.
Other question : based on what you sent and the fact you are not
familiar with crosswalk build system, I wonder how you checked out
crosswalk-6 as this is not necessarily a straightforward operation?
Question (1): Am I safe to skip this part of the build process and hard
code a None return value because
I'm using Linux?
Question (2): Are there pre-built versions of Crosswalk with media
activated, so I can avoid having to build
from source?
There are couple of codecs that we can't ship by default due to
various problems with patents and licenses. We enable the ones we can.
But what do you mean by media? We do support playing a video or an
audio file for example (depends the type and the codec).
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
