summaryrefslogtreecommitdiffstats
path: root/core/executable_internal.mk
Commit message (Collapse)AuthorAgeFilesLines
* Add LOCAL_NO_LIBGCC.Ying Wang2015-07-161-0/+4
| | | | | | | | This can be used to compile independent libraries without the need for libgcc.a. Change-Id: I924200995569d9a978ddbaa6ec321d80734f1374 (cherry picked from commit 75011b2003733edc483a45d61f5cb1a23f64bfbf)
* Use prebuilt libclang_rt.profile.Dan Albert2015-04-011-0/+2
| | | | | Bug: 17574078 Change-Id: I4838cd5d125a0b2bf76aad2fdaef1ee3122687e8
* resolved conflicts for merge of 326f9450 to lmp-dev-plus-aospDan Albert2014-09-241-0/+2
|\ | | | | | | Change-Id: I66360da623a6e7ac04610c3252f24ed69f7e4b1e
| * Add option for generating coverage info.Dan Albert2014-09-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To enable building with coverage, the environment variable NATIVE_COVERAGE must be set to true. Set `LOCAL_NATIVE_COVERAGE := true` to generate coverage information for a given component. This is currently not supported for clang (b/17574078, b/17583330). If static library A is included in a binary B (dynamic or static executable, or shared library), and A is built with coverage information, B is required to link with libgcov.a. Since the make does not offer a good way to track this dependency, link libgcov.a even if LOCAL_NATIVE_COVERAGE is not set (but still guarded by NATIVE_COVERAGE). This ensures that all of the libgcov dependencies will always be resolved, and causes no change in the resulting binary if coverage is not used. Bug: 10134489 Change-Id: Id5a19f2c215e4be80e6eae27ecc19b582f2f6813
* | am b9add847: am 53e95027: Merge "Add LOCAL_POST_LINK_CMD."Ying Wang2014-09-051-0/+2
|\ \ | |/ | | | | | | * commit 'b9add847ee1eade4ff517655decfc1790bb77d60': Add LOCAL_POST_LINK_CMD.
| * Add LOCAL_POST_LINK_CMD.Ying Wang2014-09-051-0/+2
| | | | | | | | | | | | | | | | | | For now we support LOCAL_POST_LINK_CMD only for static executables. This fixed the hack of building linker which need to insert additional step after link. Bug: 17403674 Change-Id: Iefdfe1e3fab3a30c5d4ad701d46f931481eab572
| * Add compile time check for statically linked libcDmitriy Ivanov2014-08-151-0/+7
| | | | | | | | | | | | | | | | Bug: 17047392 (cherry picked from commit 655d6851f308ad890193787a848b003685d3df9c) Change-Id: Ia824137e690b9bca1688a7603254273a737ddcbb
* | Add compile time check for statically linked libcDmitriy Ivanov2014-08-151-0/+7
| | | | | | | | | | Bug: 17047392 Change-Id: I2718422e1832ec5df7f362812ae2728dfd939076
* | Update the FDO support:Dehao Chen2014-07-301-2/+0
|/ | | | | | | | * Explicitly check BUILD_FDO_INSTRUMENT and BUILD_FDO_OPTIMIZE with true * Remove unnecessary target_libgcov * Update the profile collection path on device so that most app can have write access Change-Id: I5c1915a12ea37b2cb3c76a27e7104e47ad636928
* Add -latomic to all target buildsAndrew Hsieh2014-05-291-0/+2
| | | | | | | | | | | | | Projects using stdatomic.h needs libatomic.a in case compiler can't expand all __atomic* intrinsics. eg, __atomic_is_lock_free in armeabi/mips. Adding libatomic.a globally makes more sense than adding "LOCAL_LDLIB += -latomic " in each project including <stdatomic.h>. Projects don't need atomic operations won't get redundant DT_NEEDED entry because libatomic.a is not a shared library. Change-Id: I81dbf524544c848e667e18ab5eeabff75b5063ef
* Rename my_ndk_version_root to my_ndk_sysroot; and _include and _libAndrew Hsieh2014-04-251-4/+4
| | | | | | | | | | prebuilts/ndk/current/platforms/android-19/arch-x86_64/usr/lib is renamed to usr/lib64 to be more consistent with rest of lib paths in x86_64 toolchain, which is multilib See https://android-review.googlesource.com/#/c/92441/ Change-Id: I4e59245505d0fa87ae3608e81e715ccfcecc5ec8
* Remove redundant my_target_global_ldflagsDmitriy Ivanov2014-04-011-5/+0
| | | | | | | * Fix: my_target_global_ldflags is defined in binary.mk so they effectivelly override previous definition Change-Id: I9c7d9bde82c3a6d25a94ae109fa71ecaa33640b0
* Fix prebuilt library dependency for multilib buildYing Wang2014-02-251-1/+1
| | | | | | | Also we don't need to include module_arch_supported.mk again, if we are currently substituting the source build with LOCAL_PREBUILT_MODULE_FILE. Change-Id: I444b0397d74c3153b398a050b762e49418062a86
* Make -rpath-link work with multilib.Ying Wang2014-02-211-0/+1
| | | | Change-Id: If69ea6ed6cdbb657ed4005f8217d653e29626783
* Refactor llvm_config.mk and support the 2nd archYing Wang2014-02-071-1/+1
| | | | | | | | | 1. Following the setup of gcc in build/core/combo/, we added the [HOST|TARGET]_<arch>.mk clang config files, and load only the configs needed by the current product. 2. Added support for the 2nd arch. Change-Id: I2a383418a9688a050b39492f8e489d40eeeb5f2d
* Support to build executables for TARGET_2ND_ARCHYing Wang2014-01-241-0/+69
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
generated by cgit v1.1 at 2024-05-28 06:18:36 +0000