tequilaOS/platform_build
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_build/core/prebuilt.mk

97 lines
2.8 KiB
Makefile
Raw Normal View History

auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
###########################################################
## Standard rules for copying files that are prebuilt
##
## Additional inputs from base_rules.make:
## None.
add feature to strip "# comment" lines from prebuilt files Change things so that when $(LOCAL_PREBUILT_STRIP_COMMENTS) is nonempty, we copy the source file using sed to strip out all the "# line"-style comments and blank lines, saving considerable system image space in the case of some wifi configurations. Bug: 2036961
2009-08-06 22:02:19 +02:00
##
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
###########################################################
Record module type statistics Creates a build_system_stats.txt build artifact that contains statistics on how many BUILD_* modules are defined in a build. Also writes out information about the Soong module types sent from the Soong build. Merged-In: Iaf0c7062f542dc6942b5349854f3d49267cac4a5 Change-Id: Iaf0c7062f542dc6942b5349854f3d49267cac4a5
2016-07-26 01:03:53 +02:00
$(call record-module-type,PREBUILT)
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
Fix OVERRIDE_BUILT_MODULE_PATH for prebuilt shared libraries. So that prebuilt shared libraries can be referenced with the module name in other module's Android.mk. Change-Id: I4c4b471696642694b805b71dd7605b91724ad924
2011-09-15 21:00:52 +02:00
ifdef LOCAL_IS_HOST_MODULE
Support host multilib build 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
2014-04-17 19:03:35 +02:00
my_prefix := HOST_
Add HOST_CROSS_OS Instead of using recursive make to change the HOST_OS when building the windows SDK under linux, add the concept of cross-building to another host os. Bug: 23566667 Change-Id: I6dc525b601b6251d458d197c30bf4660d7485502
2015-08-14 21:59:50 +02:00
LOCAL_HOST_PREFIX :=
Support host multilib build 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
2014-04-17 19:03:35 +02:00
else
my_prefix := TARGET_
Support x86+arm multilib build. Support TARGET_2ND_ARCH as the binary translation arch. See target/board/generic_x86_arm/BoardConfig.mk and target/product/aosp_x86_arm.mk as example for the setup. In BoardConfig, use the TARGET_2ND_ARCH/etc. variables to set up the binary translation arch; Set "TARGET_TRANSLATE_2ND_ARCH := true" to tell the build system it's not a typical 64-bit multilib configuration. In product makefile, use "PRODUCT_PACKAGES += libfoo_<2nd_arch>" to install the TARGET_2ND_ARCH libraries. This also pulls in any dependency libraries. By default we don't install any TARGET_2ND_ARCH modules, unless it's pulled in by PRODUCT_PACKAGES. Bug: 27526885 Change-Id: I0578e9c80da0532d2fa886a8fcdb140bbc703009 (cherry-pick from commit 277e75a488b1b6599482aed9f7c046747baa10df)
2016-03-17 03:53:19 +01:00
ifeq ($(TARGET_TRANSLATE_2ND_ARCH),true)
Allow arm prebuilts for x86_arm builds But only for static and shared libraries -- we disable building other types of modules for arm, so don't support the prebuilts for them either. This is needed so that we can build these libraries under Soong, and expose them to Make using BUILD_PREBUILT. Bug: 27526885 Change-Id: I4f6ec922aed37591b6257b7022b81fb65d05b0fe
2016-05-31 22:59:38 +02:00
# Only support prebuilt shared and static libraries for translated arch
ifeq ($(filter SHARED_LIBRARIES STATIC_LIBRARIES,$(LOCAL_MODULE_CLASS)),)
LOCAL_MULTILIB := first
endif
Support x86+arm multilib build. Support TARGET_2ND_ARCH as the binary translation arch. See target/board/generic_x86_arm/BoardConfig.mk and target/product/aosp_x86_arm.mk as example for the setup. In BoardConfig, use the TARGET_2ND_ARCH/etc. variables to set up the binary translation arch; Set "TARGET_TRANSLATE_2ND_ARCH := true" to tell the build system it's not a typical 64-bit multilib configuration. In product makefile, use "PRODUCT_PACKAGES += libfoo_<2nd_arch>" to install the TARGET_2ND_ARCH libraries. This also pulls in any dependency libraries. By default we don't install any TARGET_2ND_ARCH modules, unless it's pulled in by PRODUCT_PACKAGES. Bug: 27526885 Change-Id: I0578e9c80da0532d2fa886a8fcdb140bbc703009 (cherry-pick from commit 277e75a488b1b6599482aed9f7c046747baa10df)
2016-03-17 03:53:19 +01:00
endif
Support host multilib build 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
2014-04-17 19:03:35 +02:00
endif
add support for LOCAL_MULTILIB LOCAL_MULTILIB replaces LOCAL_32_BIT_ONLY and LOCAL_NO_2ND_ARCH, although both are still supported. Set LOCAL_MULTILIB := 32 to always build a module 32-bit. This is the same as specifying LOCAL_32_BIT_ONLY. Set LOCAL_MULTILIB := first to always build a module for the first architecture (64-bit on a 64-bit target, 32-bit on a 32-bit target). This is the same as specifying LOCAL_NO_2ND_ARCH. Set LOCAL_MULTILIB := both to build for both architectures on a mulitlib (64-bit) target. If LOCAL_MULTILIB is not set libraries will default to "both", and executables, packages, and prebuilts will default to building for the first architecture if supported by the module, otherwise the second. Executables that set LOCAL_MULTILIB := both must set either LOCAL_MODULE_STEM_32 and LOCAL_MODULE_STEM_64 or LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 to specify how to differentiate the install locations of the two versions. Change-Id: I22ab6aa342b231c307b1d8a86cea4fd91eea39f5
2014-03-21 20:29:32 +01:00
include $(BUILD_SYSTEM)/multilib.mk
Real "LOCAL_MULTILIB := both" for prebuilts This uses the fact that unsetting LOCAL_MULTILIB equals "either". It's useful to build for both 32-bit and 64-bit in the same prebuilt module definition. Bug: 13751317 Change-Id: I4f1625a83e13f22f807039afebae73f69ed35918
2014-05-16 19:38:43 +02:00
my_skip_non_preferred_arch :=
add support for LOCAL_MULTILIB LOCAL_MULTILIB replaces LOCAL_32_BIT_ONLY and LOCAL_NO_2ND_ARCH, although both are still supported. Set LOCAL_MULTILIB := 32 to always build a module 32-bit. This is the same as specifying LOCAL_32_BIT_ONLY. Set LOCAL_MULTILIB := first to always build a module for the first architecture (64-bit on a 64-bit target, 32-bit on a 32-bit target). This is the same as specifying LOCAL_NO_2ND_ARCH. Set LOCAL_MULTILIB := both to build for both architectures on a mulitlib (64-bit) target. If LOCAL_MULTILIB is not set libraries will default to "both", and executables, packages, and prebuilts will default to building for the first architecture if supported by the module, otherwise the second. Executables that set LOCAL_MULTILIB := both must set either LOCAL_MODULE_STEM_32 and LOCAL_MODULE_STEM_64 or LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 to specify how to differentiate the install locations of the two versions. Change-Id: I22ab6aa342b231c307b1d8a86cea4fd91eea39f5
2014-03-21 20:29:32 +01:00
# check if first arch is supported
Reset LOCAL_2ND_ARCH_VAR_PREFIX before referencing it. Change-Id: I9182ce1efe09609100d19c9fae2bc4fe7358dfc0
2014-10-22 03:34:30 +02:00
LOCAL_2ND_ARCH_VAR_PREFIX :=
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
include $(BUILD_SYSTEM)/module_arch_supported.mk
ifeq ($(my_module_arch_supported),true)
add support for LOCAL_MULTILIB LOCAL_MULTILIB replaces LOCAL_32_BIT_ONLY and LOCAL_NO_2ND_ARCH, although both are still supported. Set LOCAL_MULTILIB := 32 to always build a module 32-bit. This is the same as specifying LOCAL_32_BIT_ONLY. Set LOCAL_MULTILIB := first to always build a module for the first architecture (64-bit on a 64-bit target, 32-bit on a 32-bit target). This is the same as specifying LOCAL_NO_2ND_ARCH. Set LOCAL_MULTILIB := both to build for both architectures on a mulitlib (64-bit) target. If LOCAL_MULTILIB is not set libraries will default to "both", and executables, packages, and prebuilts will default to building for the first architecture if supported by the module, otherwise the second. Executables that set LOCAL_MULTILIB := both must set either LOCAL_MODULE_STEM_32 and LOCAL_MODULE_STEM_64 or LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 to specify how to differentiate the install locations of the two versions. Change-Id: I22ab6aa342b231c307b1d8a86cea4fd91eea39f5
2014-03-21 20:29:32 +01:00
# first arch is supported
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
include $(BUILD_SYSTEM)/prebuilt_internal.mk
Real "LOCAL_MULTILIB := both" for prebuilts This uses the fact that unsetting LOCAL_MULTILIB equals "either". It's useful to build for both 32-bit and 64-bit in the same prebuilt module definition. Bug: 13751317 Change-Id: I4f1625a83e13f22f807039afebae73f69ed35918
2014-05-16 19:38:43 +02:00
ifneq ($(my_module_multilib),both)
my_skip_non_preferred_arch := true
endif # $(my_module_multilib)
Don't set up the prebuilt apk rule twice. For apps, we don't want to set up the prebuilt apk rule twice even if "LOCAL_MULTILIB := both", which for apps really means to set up only the jni library rules twice. See also build/core/install_jni_libs.mk. Change-Id: Id0406c3c605c6ede613dba06178a1710590c09b3
2014-12-02 00:56:19 +01:00
# For apps, we don't want to set up the prebuilt apk rule twice even if "LOCAL_MULTILIB := both".
ifeq (APPS,$(LOCAL_MODULE_CLASS))
my_skip_non_preferred_arch := true
endif
Real "LOCAL_MULTILIB := both" for prebuilts This uses the fact that unsetting LOCAL_MULTILIB equals "either". It's useful to build for both 32-bit and 64-bit in the same prebuilt module definition. Bug: 13751317 Change-Id: I4f1625a83e13f22f807039afebae73f69ed35918
2014-05-16 19:38:43 +02:00
endif # $(my_module_arch_supported)
ifndef my_skip_non_preferred_arch
ifneq (,$($(my_prefix)2ND_ARCH))
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
# check if secondary arch is supported
Support host multilib build 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
2014-04-17 19:03:35 +02:00
LOCAL_2ND_ARCH_VAR_PREFIX := $($(my_prefix)2ND_ARCH_VAR_PREFIX)
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
include $(BUILD_SYSTEM)/module_arch_supported.mk
ifeq ($(my_module_arch_supported),true)
# secondary arch is supported
Real "LOCAL_MULTILIB := both" for prebuilts This uses the fact that unsetting LOCAL_MULTILIB equals "either". It's useful to build for both 32-bit and 64-bit in the same prebuilt module definition. Bug: 13751317 Change-Id: I4f1625a83e13f22f807039afebae73f69ed35918
2014-05-16 19:38:43 +02:00
OVERRIDE_BUILT_MODULE_PATH :=
LOCAL_BUILT_MODULE :=
LOCAL_INSTALLED_MODULE :=
LOCAL_INTERMEDIATE_TARGETS :=
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
include $(BUILD_SYSTEM)/prebuilt_internal.mk
Real "LOCAL_MULTILIB := both" for prebuilts This uses the fact that unsetting LOCAL_MULTILIB equals "either". It's useful to build for both 32-bit and 64-bit in the same prebuilt module definition. Bug: 13751317 Change-Id: I4f1625a83e13f22f807039afebae73f69ed35918
2014-05-16 19:38:43 +02:00
endif # $(my_module_arch_supported)
endif # $($(my_prefix)2ND_ARCH)
endif # $(my_skip_non_preferred_arch) not true
Set up rules to build prebuilts for TARGET_2ND_ARCH Prebuilts built for the 2nd arch will install into 2nd arch directories. Change-Id: I3d020a3c1fb0f2eb0579933f8a66e410e66fdd44
2014-01-24 22:34:51 +01:00
LOCAL_2ND_ARCH_VAR_PREFIX :=
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
Add HOST_CROSS_OS Instead of using recursive make to change the HOST_OS when building the windows SDK under linux, add the concept of cross-building to another host os. Bug: 23566667 Change-Id: I6dc525b601b6251d458d197c30bf4660d7485502
2015-08-14 21:59:50 +02:00
ifdef LOCAL_IS_HOST_MODULE
ifdef HOST_CROSS_OS
Add NATIVE_TESTS class, move host native tests Host native tests have been getting installed into out/host/linux-x86/bin/..., but this pollutes the bin directory with a lot of poorly named tests. Also, to support 32-bit and 64-bit tests, we need to have different names with different suffixes. This causes problems when tests expect to be named something specific (like gtest). It's also convenient to store test data next to the test itself. So with this change, native tests will be installed in out/host/linux-x86/nativetest[64]/$(LOCAL_MODULE)/$(LOCAL_MODULE_STEM) just like target tests get installed into /data/nativetest[64]. Implement this using a new NATIVE_TESTS class, which is like EXECUTABLES, but sets up the install path differently, and configures the rpath to load shared libraries with the proper relative path. LOCAL_MODULE_RELATIVE_PATH can be used to control the directory name, it will default to $(LOCAL_MODULE). This way multiple related tests can be grouped together. Target native tests also use NATIVE_TESTS now, but nothing should change other than LOCAL_MODULE_RELATIVE_PATH can be used. Change-Id: I535e42b1a6b21c5b8d6a580aa2f944d2be35e27d
2016-03-02 22:54:51 +01:00
ifneq (,$(filter EXECUTABLES STATIC_LIBRARIES SHARED_LIBRARIES NATIVE_TESTS,$(LOCAL_MODULE_CLASS)))
Add HOST_CROSS_OS Instead of using recursive make to change the HOST_OS when building the windows SDK under linux, add the concept of cross-building to another host os. Bug: 23566667 Change-Id: I6dc525b601b6251d458d197c30bf4660d7485502
2015-08-14 21:59:50 +02:00
my_prefix := HOST_CROSS_
LOCAL_HOST_PREFIX := $(my_prefix)
include $(BUILD_SYSTEM)/module_arch_supported.mk
ifeq ($(my_module_arch_supported),true)
# host cross compilation is supported
OVERRIDE_BUILT_MODULE_PATH :=
LOCAL_BUILT_MODULE :=
LOCAL_INSTALLED_MODULE :=
LOCAL_INTERMEDIATE_TARGETS :=
include $(BUILD_SYSTEM)/prebuilt_internal.mk
endif
LOCAL_HOST_PREFIX :=
endif
Tell Soong about HOST_CROSS_* This configures Soong to build windows binaries, which requires support for 64-bit windows binaries in BUILD_PREBUILT for USE_SOONG=true. module_arch_supported.mk did not support 64-bit being the secondary architecture when evaluating multilib conditionals. All other uses of HOST_*_IS_64_BIT already check the proper version. Change-Id: Iff664733e6991f4adbe8ddd620b091bbb55d1d86
2016-02-09 23:55:13 +01:00
ifdef HOST_CROSS_2ND_ARCH
my_prefix := HOST_CROSS_
LOCAL_2ND_ARCH_VAR_PREFIX := $($(my_prefix)2ND_ARCH_VAR_PREFIX)
LOCAL_HOST_PREFIX := $(my_prefix)
include $(BUILD_SYSTEM)/module_arch_supported.mk
ifeq ($(my_module_arch_supported),true)
OVERRIDE_BUILT_MODULE_PATH :=
LOCAL_BUILT_MODULE :=
LOCAL_INSTALLED_MODULE :=
LOCAL_INTERMEDIATE_TARGETS :=
include $(BUILD_SYSTEM)/prebuilt_internal.mk
endif
LOCAL_HOST_PREFIX :=
LOCAL_2ND_ARCH_VAR_PREFIX :=
endif
Add HOST_CROSS_OS Instead of using recursive make to change the HOST_OS when building the windows SDK under linux, add the concept of cross-building to another host os. Bug: 23566667 Change-Id: I6dc525b601b6251d458d197c30bf4660d7485502
2015-08-14 21:59:50 +02:00
endif
endif
support LOCAL_MODULE_TARGET_ARCH for prebuilts Prebuilts often support only a single architecture, allow them to use LOCAL_MODULE_TARGET_ARCH to specify it. Change-Id: I2514f66f682ef267bbf1a1ab78510faff0a18b64
2014-02-14 00:04:18 +01:00
my_module_arch_supported :=
Reference in a new issue Copy permalink