We use 32-bit libraries because there's a fair amount of Android code
that is compiled both for the target device and for the host at build
time, and building the host variants as 32-bit allows to have closer
behaviors between the host and the device. In addition, some host
tools are known to only work in 32-bit, e.g. the emulator itself.
JBQ
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
We use 32-bit libraries because there's a fair amount of Android code
that is compiled both for the target device and for the host at build
time, and building the host variants as 32-bit allows to have closer
behaviors between the host and the device. In addition, some host
tools are known to only work in 32-bit, e.g. the emulator itself.
As for the emulator, it's fundamentally a JIT, and running it as
64-bit would require having a JIT that can output 64-bit code.
JBQ