I don't have access to a Mac right now to verify what works and what doesn't. Generally, "make android" is the right way to build Android binaries, it is neither deprecated nor known to be broken. However, I've tested it only on Linux AFAIR.
In the meantime, please run "make android V=1" and post the entire output (via pastebin if it's too much for an email). "make arm" is different. It builds binaries that run on x86 host systems using V8's own ARM simulator. On Tue, Mar 6, 2012 at 18:38, LDS <[email protected]> wrote: > I've got a problem using gyp on MacOS X to make an android v8 lib. > > First I can correctly build v8 on host since I set up the generator to > make. > > Then when I run "make android" and get this: > > arm-linux-androideabi-g++: i386: No such file or directory > > My ANDROID_NDK_ROOT is set correctly to the latest NDK (v7), I ran the > installdir inside NDK as suggested on the wiki, and finally, I > verified internally in the make command that ANDROID_TOOL_PREFIX > points to the cross-compiled toolchain bins. > > I haven't look deeper yet, but it seems that Make-android strips g++ > and friends from the absolute path. At least this seems to be the only > explanation now, as Make-android is entered with the right options. > > Now "make arm" works fine. So is it the "new" recommended way to > build v8 android? > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
