Hi all,

*Some background:*

I am one of the authors of MuPDF, a cross platform open source PDF viewer. 
Recently we have been adding support for form filling etc, which requires 
the use of javascript for validation etc. We've been using v8 (version 3.9) 
for a while, and it works fine on Windows/MacOS/Linux and Android 
armeabi-v7a.

We've just had it pointed out to us that it fails on armeabi though - the 
app falls over trying to load libmupdf.so. This is generated by linking our 
object files, plus all the static libraries we use (including v8).

The fact it falls over on armeabi is probably not surprising as we 
currently only have libv8_base.a and libv8_snapshot.a (the v8 libraries we 
use) built as armeabi-v7a, whereas all the other libraries/files are built 
for both armeabi and armeabi-v7a.

So I've modified the makefiles to link with different versions of the v8 
libs. The problem is, we are still falling over at load time. So it seems 
likely I've made a mess of building the armeabi v8 libs.

*So, The question:*

How do I build v8 (preferably version 3.9, but any version would do at this 
point) for armeabi rather than armeabi-v7a?

On v3.9 I do:

make android                 (to make the armeabi-v7a ones)
make android.clean
make android armv7=0    (to make the armeabi ones)

but they are suspiciously similarly sized.

With the current git HEAD, I had to modify the calls a bit:

For armeabi-v7a I do:

make -j8 GYPFLAGS="-Dcomponent=static_library" android_arm.release

make -j8 GYPFLAGS="-Dcomponent=static_library" android_arm.clean

make -j8 GYPFLAGS="-Dcomponent=static_library" armv7=0 android_arm.release

but again, they are suspiciously similarly sized.

Any help people can give would be much appreciated!

Thanks,

Robin

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to