summaryrefslogtreecommitdiffstats
path: root/core/executable.mk
Commit message (Collapse)AuthorAgeFilesLines
* Support host multilib buildYing Wang2014-05-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* build: split TARGET_PREFER_32_BIT for apps and executablesColin Cross2014-04-301-3/+3
| | | | | | | | | Introduce two new flags, TARGET_PREFER_32_BIT_APPS and TARGET_PREFER_32_BIT_EXECUTABLES that individually control compilation of apps and executables. If TARGET_PREFER_32_BIT is set, the build system will automatically set both new flags. Change-Id: Ibd2165e688675c2884d9e7ddf82d7dd6c28521f3
* build: fix TARGET_PREFER_32_BITColin Cross2014-04-101-21/+24
| | | | | | | | | | | TARGET_PREFER_32_BIT can't assume that the 32-bit rule is allowed, it needs to try the 32-bit rule first, then fall back to the 64-bit rule in case the module specifies LOCAL_MODULE_TARGET_ARCH or LOCAL_MODULE_UNSUPPORTED_TARGET_ARCH to disallow the 32-bit build. Also port TARGET_PREFER_32_BIT to package.mk. Change-Id: I07520b75c4ee11a1e95a82b3afa2a33d4907eb04
* add support for LOCAL_MULTILIBColin Cross2014-03-261-7/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* add support for module supported or unsupported target architecturesColin Cross2014-02-121-5/+16
| | | | | | | | | | | | | | | | | | | | | | Add four new variables for module makefiles: LOCAL_MODULE_TARGET_ARCH specifies that a module is only supported for one or more architectures. Any architecture not in the list will be not attempt to build the module. The expected use case is prebuilts that are only suitable for a single architecture, or modules like llvm that need per-architecture support. LOCAL_MODULE_UNSUPPORTED_TARGET_ARCH specifies that a module cannot be built for one or more architectures. LOCAL_MODULE_TARGET_ARCH_WARN and LOCAL_MODULE_UNSUPPORTED_TARGET_ARCH_WARN are the same, but warn that the arch is not supported, which is useful for modules that are critical but not yet working. The logic for whether or not to build an architecture is fairly complicated, so this patch consolidates it into module_arch_supported.mk Change-Id: I120caf4a375f484e1fd6017b60c2f53882ae01e6
* Refine module name resolving in multilib buildYing Wang2014-02-101-0/+6
| | | | | | | | | | | | | | | | | | | | | | -- Added TARGET_PREFER_32_BIT, which sets LOCAL_32_BIT_ONLY for an executable, if LOCAL_NO_2ND_ARCH is not true. Name resolving in 64-bit multilib build: -- Name resolving in PRODUCT_PACKAGES: foo:32 resolves to foo_32; foo:64 resolves to foo; foo resolves to both foo and foo_32 (if foo_32 is defined). -- Name resolving for LOCAL_REQUIRED_MODULES: If a module is built for 2nd arch, its required module resolves to 32-bit variant, if it exits; Otherwise for executable and shared library, a required module resolves to the default 64-bit variant; for other module classes, required module foo resolves to both foo and foo_32 (if foo_32 is defined) Bug: 12898862 Change-Id: I5fda1a77f58814097b10b5ad2743ee25adfaecc4
* don't rename 32-bit executables to *_32Colin Cross2014-02-041-0/+2
| | | | | | | Renaming 32-bit executables to *_32 breaks PRODUCT_PACKAGES dependencies. Change-Id: I53d89991633ef4af03c4e618c463769937a70e38
* build: rename LOCAL_32BIT_ONLY to LOCAL_32_BIT_ONLYColin Cross2014-01-291-2/+2
| | | | | | Rename for consistency with TARGET_IS_64_BIT. Change-Id: I824dcaed0c1e88b8246bcffb21ab3f1772175926
* Support to build executables for TARGET_2ND_ARCHYing Wang2014-01-241-65/+9
| | | | | | | | | | | By default, an executable is built for TARGET_ARCH. To build it for TARGET_2ND_ARCH in a 64bit product, use: LOCAL_32BIT_ONLY := true To skip a module for TARGET_2ND_ARCH, use: LOCAL_NO_2ND_ARCH := true Bug: 11654773 Change-Id: Ieb293d25b21024bfe1b554044df338e064ac7b46
* Remove aprof support from the build system.Ying Wang2014-01-141-11/+0
| | | | | | This reverts the commit 70dc3e1d. Change-Id: I480b005579805d2608d05dac41e32bb44642e813
* Allow clang to build host binaries.Logan Chien2014-01-071-0/+4
| | | | Change-Id: I7e4f9dc6f69a97cfefdfa2ed55c5d7b8ad496da7
* Support to switch between prebuilt and buiding from sourceYing Wang2013-01-151-0/+13
| | | | | | For target shared library and executable. Change-Id: I40a4e4e0c971811ac60e9bd04206f2422387d3d0
* Support to build executables against the NDKYing Wang2012-09-251-3/+31
| | | | | | | | Use "LOCAL_SDK_VERSION := <number>" to build against the NDK when you include $(BUILD_EXECUTABLE). Bug: 7170098 Change-Id: I4cebeae3355e79a4d2f2f5549ef0613ced77e3f0
* Profiling use aprof, enable by LOCAL_ENABLE_APROF or LOCAL_ENABLE_APROF_JNIKito Cheng2012-06-151-0/+12
| | | | Change-Id: Ia95dc7318e17c0804867b22e239edccc5cbec0af
* build: remove prelinker build build systemIliyan Malchev2011-03-121-5/+0
| | | | | | | | | | | | | | | | | | | | This patch removes support for prelinking from the build system. By now, the prelinker has outlived its usefulness for several reasons. Firstly, the speedup that it afforded in the early days of Android is now nullified by the speed of hardware, as well as by the presence of Zygote. Secondly, the space savings that come with prelinking (measued at 17MB on a recent honeycomb stingray build) are no longer important either. Thirdly, prelinking reduces the effectiveness of Address-Space-Layout Randomization. Finally, since it is not part of the gcc suite, the prelinker needs to be maintained separately. The patch deletes apriori, soslim, lsd, isprelinked, and iself from the source tree. It also removes the prelink map. LOCAL_PRELINK_MODULE becomes a no-op. Individual Android.mk will get cleaned separately. Support for prelinking will have to be removed from the recovery code and from the dynamic loader as well. Change-Id: I5839c9c25f7772d5183eedfe20ab924f2a7cd411
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-0/+28
|
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-28/+0
|
* Initial ContributionThe Android Open Source Project2008-10-211-0/+28
generated by cgit v1.1 at 2024-05-19 11:26:04 +0000