I have similar problems when building. The part the worries me is the environment setup. I'm still confused about the steps as each one of them refers to a general build page of chromium leaving me in a sea of unknown.
I really need to make modifications for android and in our case scenario to make xwalk functional. Mostly because of hardcoded native library paths (xwalkviewdelegate) and lack of control over the initialization flow. For example how and where to load the .so file and what to do if the .so is in another directory rather than the default data/data/lib. On 22 May 2015 14:49, "Alexander Biemann" <[email protected]> wrote: > Thanks for your previous help - I do want to propose a bug fix, but first > I want to test that the bug fix is reasonable. > > However, I'm running into a lot of trouble building Crosswalk on a MacBook > Pro with OSX 10.10 (it has taken 2 days already) > For example, on the page > https://crosswalk-project.org/contribute/building_crosswalk.html *none* > of it results *without* an error message. > Is it expected to work (build) on a Mac ? > > > Alexs-MacBook-Pro-2:src Alex.Biemann$ pwd > > /Users/Alex.Biemann/crosswalk-src/src > > Alexs-MacBook-Pro-2:src Alex.Biemann$ sudo > ./build/install-build-deps-android.sh > > Password: > > ERROR: lsb_release not found in $PATH > > Alexs-MacBook-Pro-2:src Alex.Biemann$ sudo yum install alsa-lib-devel > alsa-lib-devel.i686 bison cairo-devel.i686 cups-devel cups-devel.i686 > dbus-devel dbus-devel.i686 elfutils-libelf-devel.i686 > elfutils-libelf-devel.x86_64 expat-devel expat-devel.i686 > fontconfig-devel.i686 freetype-devel.i686 gcc-c++ gconf GConf2-devel > GConf2-devel.i686 gconf-devel git glib2-devel.i686 glibc-devel.i686 gperf > gtk2-devel harfbuzz-devel.i686 krb5-devel.i686 libcap-devel > libcap-devel.i686 libcom_err-devel.i686 libgcrypt-devel > libgcrypt-devel.i686 libgnome-keyring-devel libgpg-error-devel.i686 > libgudev1-devel libpciaccess-devel libstdc++.i686 libX11-devel.i686 > libXcomposite-devel.i686 libXcursor-devel.i686 libXdamage-devel.i686 > libXext-devel.i686 libXfixes-devel.i686 libXi-devel.i686 > libXrandr-devel.i686 libXrender-devel.i686 libXScrnSaver-devel > libXtst-devel libXtst-devel.i686 lighttpd nss-devel nss.i686 > pango-devel.i686 pciutils-devel pciutils-devel.i686 pulseaudio-libs-devel > python-pexpect svn systemd-devel systemd-devel.i686 xorg-x11-server-Xvfb > xorg-x11-utils zlib-devel.i686 zlib.i686 > > sudo: yum: command not found > > Alexs-MacBook-Pro-2:src Alex.Biemann$ cd .. > > Alexs-MacBook-Pro-2:crosswalk-src Alex.Biemann$ echo "{ 'GYP_DEFINES': > 'OS=android target_arch=arm', }" > chromium.gyp_env > > Alexs-MacBook-Pro-2:crosswalk-src Alex.Biemann$ cat ./chromium.gyp_env > > { 'GYP_DEFINES': 'OS=android target_arch=arm', } > > Alexs-MacBook-Pro-2:crosswalk-src Alex.Biemann$ . > ./xwalk/build/android/envsetup.sh > > -bash: ./xwalk/build/android/envsetup.sh: No such file or directory > > Alexs-MacBook-Pro-2:crosswalk-src Alex.Biemann$ cd src > > Alexs-MacBook-Pro-2:src Alex.Biemann$ . ./xwalk/build/android/envsetup.sh > > readlink: illegal option -- f > > usage: readlink [-n] [file ...] > > Warning: Current directory is out of CHROME_SRC, it may not be the one > you want. > > > Alexs-MacBook-Pro-2:src Alex.Biemann$ > > > > How do I continue with the build process ? > > > > From: [email protected] > > To: [email protected] > > CC: [email protected]; [email protected] > > Subject: Re: [Crosswalk-help] Building from source - ambiguity in wiki > > Date: Tue, 19 May 2015 11:06:00 +0300 > > > > "Kapade, Mrunal" <[email protected]> writes: > > > > > Hi Alexander, > > > > > > Sorry for the confusion but you are looking at old Android Build page > which should have been taken off I think. > > > Anyway you can follow the latest updated build instructions here on > > > Crosswalk website, > > > https://crosswalk-project.org/contribute/building_crosswalk.html > > > > > > The "src" directory referred in the build instructions typically > > > refers to the "src" directory which contains the Chromium code. For > > > example you created a directory for crosswalk development at > > > ~/crosswalk > > > then after initial gclient sync it would have created a src folder at > > > ~/crosswalk/src > > > which holds the chromium code. > > > Within that "src" directory there will also be a directory for > Crosswalk specific sources at, > > > ~/crosswalk/src/xwalk. > > > I hope this explains the "src" directory. > > > > > > I guess you want to modify the Crosswalk source to fix a bug. Once you > > > have tested your fix you are welcome to submit a pull request to > > > crosswalk repo. > > > > Mrunal is correct, and to prevent further confusion I've removed that > > outdated page from the wiki. > > > > Please let us know if you still have any problems building the source > > code. > > _______________________________________________ > 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
