build.git - build

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove ancient ranlib workaround on Mac OS X.	Ying Wang	2015-04-09	1	-5/+0
\| \| \| \| \| \|	Apparently we don't need it for Mac OS X 10.7 and above. Change-Id: I5ee81700c16e8c66b2d5f2b373fd2d523b5ec018
*	Fix building on modern versions of Xcode and OS X.	Al Sutton	2014-11-10	1	-0/+1
\| \| \| \| \| \| \| \| \|	Add the build options to support the most recent versions of XCode and add 10.9 to the list of OS X SDKs which the AOSP code can be built with. Based on patch from https://groups.google.com/d/msg/android-building/kePgJmYBUdM/0C_d1OZflvcJ Change-Id: I97ffe45d3c54a095952a4ac6accb938623b8fa1e Signed-off-by: Al Sutton <al@funkyandroid.com>
*	Remove unnecessary 10.8-specific build rules	Stephen Hines	2014-10-17	1	-5/+0
\| \| \| \| \| \| \| \|	We no longer need gcc for host builds, since those all run through clang. This header include, however, triggers errors about SSE intrinsics by replacing the more relevant include dirs that we should be using. Change-Id: I26a949f0109de8e6e2d1f09cb8127be927549cc4
*	Use hermetic host toolchains.	Ying Wang	2014-07-28	1	-6/+0
\| \| \| \|	Change-Id: I6bb72b5728d1075be9645f8473dcf3db759fa66a
*	More consistent use of 64-bit build variable.	Ying Wang	2014-07-08	1	-2/+0
\| \| \| \| \| \| \| \|	Set up TARGET_IS_64_BIT and HOST_IS_64_BIT early so we don't need 2 mechanisms to judge if it's 64-bit build; Remove the unnecessary 32-bit host variables. Change-Id: I08d6d4d9ea70f91135fe2ee05463fb9a0d1cee42
*	Support host multilib build	Ying Wang	2014-05-14	1	-0/+80
	This change basically ported our target multilib to the host side. It supports 2 host build modes: x86 and x86_64 multilib build. For now you need to set "BUILD_HOST_64bit=true" to switch to x86_64 multilib build. Later we'll default to x86_64 build and have a flag to force 32-bit only build, which may be needed by SDK build. In host module definition, like in target ones, you can use the following LOCAL variables to set up multilib configuration: LOCAL_MULTILIB: can be "both", "first", "32" or "64". It also supports the same set of arch or 32-vs-64 specific LOCAL variables. By default, it builds only for the first arch. To keep path compatibility, in x86_64 build files are still output to out/host/linux-x86; Both 32-bit and 64-bit executables are in out/host/linux-86/bin; In x86_64 build 32-bit shared libraries are installed to out/host/linux-x86/lib32 and 64-bit shared libraries are installed to out/host/linux-x86/lib; 32-bit object files are output to out/host/linux-x86/obj32 and 64-bit object files are output to out/host/linux-x86/obj. Bug: 13751317 Change-Id: I6044f83b7db369a33e05209e8c588eb6dc83409f