Home
last modified time | relevance | path

Searched refs:build (Results 1 – 20 of 20) sorted by relevance

/bionic/tests/libs/
DAndroid.mk24 include $(LOCAL_PATH)/Android.build.dlext_testzip.mk
27 include $(LOCAL_PATH)/Android.build.dlext_testzip.mk
/bionic/benchmarks/linker_relocation/
DREADME.md9 To run the benchmark, build the `linker-reloc-bench` target, sync `data`, and
24 - with `--ninja`: generate a build.ninja instead, and build a set of ELF file
/bionic/
DCPPLINT.cfg2 filter=-build/header_guard,-runtime/int,-readability/function
Dandroid-changes-for-ndk-developers.md31 * On a developer preview build, dynamic linker warnings will also show up
98 above. (Use --hash-style=both if you want to build code that uses this
117 Some apps have bad DT_NEEDED entries (usually absolute paths on the build
233 *Resolution*: remove the extra steps from your build that strip section
300 Even worse, some build systems have bugs that cause them to insert
301 DT_NEEDED entries that point to a file on the build host, something that
310 [C:\Users\build\Android\ci\jni\libBroken.so]
316 device. There are broken third-party toolchains/build systems that use
317 a path on a build host instead of the SONAME.
329 or a misconfiguration in your build system. A missing SONAME may lead
[all …]
DREADME.md108 # This is where we keep the hacks necessary to build BSD source
187 build your device drivers, you shouldn't modify bionic. Instead use
188 …riends described in [config.mk](https://android.googlesource.com/platform/build/+/master/core/conf…
202 _not_ build the entire tree; just the minimum number of projects that are
239 Currently, the list of bionic CTS tests is generated at build time by
280 * Note that the build system is ignorant to this flag being toggled, i.e. if
299 First, build and run the host tests as usual (see above).
/bionic/tests/
Dstring_posix_strerror_r_test.cpp30 # error check whether we can build this now...
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
/bionic/benchmarks/
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
DAndroid.bp91 // We don't build a static benchmark executable because it's not usually
/bionic/tools/versioner/src/
DAndroid.bp4 defaults: ["llvm-build-host-tools-defaults"],
/bionic/libc/kernel/uapi/linux/
Dpsp-sev.h67 __u8 build; member
/bionic/build/
Drun-on-host.sh3 source ${ANDROID_BUILD_TOP}/build/envsetup.sh
/bionic/libc/kernel/
DREADME.md92 After this, you will need to build/test the tree to make sure that these
/bionic/docs/
D32-bit-abi.md45 grep thoroughly in both your source and your build system: many people
Dnative_allocator.md299 To build this benchmark:
303 This will build two executables:
Delf-tls.md612 variant 1 layout. This change shipped in NDK r14, and the NDK's build systems (ndk-build and the
825 AOSP hikey960 build, only `/system/bin/netd` has a TLS segment, and it's only 32 bytes. As long as
Dstatus.md350 build system they're using. The exact subset of FORTIFY available to
/bionic/linker/
DAndroid.bp257 // when stl is not set to "none" build system adds libdl
/bionic/libc/
DAndroid.bp1297 // to avoid infinite recursion. For the other architectures we just build an
1815 // The build system generally requires that any dependencies of a target
/bionic/libc/malloc_debug/
DREADME.md538 The new line fingerprint line is the contents of the ro.build.fingerprint