How easy would it be to add MIPS output for Android (in addition to Arm and x86 libs) ?
I'm only asking because this kind of gadget looks pretty useful and it also opens up more cheap tablets.
http://blog.imgtec.com/powervr/mips-creator-ci20-development-board-now-available
Coder, video game industry veteran (since the '80s, ❤'s assembler), arrested - never convicted hacker (in the '90s), dad of five, he/him (if that even matters!).
https://deluxepixel.com
Comments
https://deluxepixel.com
configured to little-endian only, although it's a good practice to check
endianess at runtime (or assert the fact) so your C/C++ code is more
portable."
https://deluxepixel.com
This is the name of an ABI for MIPS-based CPUs that support *at* *least* the MIPS32r1 instruction set. The ABI includes the following features:
- MIPS32 revision 1 ISA
- Little-Endian
- O32
- Hard-Float
- no DSP application specific extensions"
https://deluxepixel.com
https://deluxepixel.com
https://deluxepixel.com
https://deluxepixel.com
https://github.com/gideros/gideros/search?utf8=✓&q=armeabi+armeabi-v7a+x86
Build android libs using scripts inside scripts directory
and try it out on the mips tablet
It can't hurt as it only increased the number of devices whilst the build size will only go up slightly.
http://www.androidauthority.com/64-bit-mips-i6400-518130/
https://deluxepixel.com
APP_ABI := all
This includes all of them ?
https://deluxepixel.com
But seriously I think might be best to include them all and have the user just remove the folders containing those they don't want directly?
https://deluxepixel.com