9ecbf83259
This is mostly the same as the existing 2ND_HOST / HOST_CROSS support. The interesting thing I did here was make x86 the 'first' architecture, and x86_64 the second. This way LOCAL_MULTILIB := first defaults to 32-bit windows modules. windows-x86/bin <- defaults to 32-bit executables windows-x86/lib <- 32-bit libraries, like before windows-x86/lib64 <- 64-bit libraries windows-x86/obj <- 32-bit intermediates windows-x86/obj64 <- 64-bit intermediates Then modules are registered with the names: host_cross_liblog <- 32-bit, like before host_cross_liblog_64 <- 64-bit Bug: 26957718 Change-Id: I9f119411acb43e973ec1e6bca3c1dc291c91556c |
||
---|---|---|
.. | ||
arch | ||
fdo.mk | ||
HOST_CROSS_windows-x86.mk | ||
HOST_CROSS_windows-x86_64.mk | ||
HOST_darwin-x86.mk | ||
HOST_darwin-x86_64.mk | ||
HOST_linux-x86.mk | ||
HOST_linux-x86_64.mk | ||
javac.mk | ||
mac_version.mk | ||
select.mk | ||
TARGET_linux-arm.mk | ||
TARGET_linux-arm64.mk | ||
TARGET_linux-mips.mk | ||
TARGET_linux-mips64.mk | ||
TARGET_linux-x86.mk | ||
TARGET_linux-x86_64.mk |