Home
last modified time | relevance | path

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

/bionic/tests/prebuilt-elf-files/
Dgen-libtest_invalid-local-tls.sh19 build() { function
27 build arm armv7a-linux-androideabi29
28 build arm64 aarch64-linux-android29
29 build x86 i686-linux-android29
30 build x86_64 x86_64-linux-android29
/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.md33 * On a developer preview build, dynamic linker warnings will also show up
102 above. Use `--hash-style=both` if you want to build code that uses this
123 Some apps have bad DT_NEEDED entries (usually absolute paths on the build
229 *Resolution*: remove the extra steps from your build that strip section
296 Even worse, some build systems have bugs that cause them to insert
297 DT_NEEDED entries that point to a file on the build host, something that
306 [C:\Users\build\Android\ci\jni\libBroken.so]
312 device. There are broken third-party toolchains/build systems that use
313 a path on a build host instead of the SONAME.
323 (Shared Object Name) attribute. The NDK build systems add this
[all …]
DREADME.md131 # This is where we keep the hacks necessary to build BSD source
311 build your device drivers, you shouldn't modify bionic. Instead use
312 …riends described in [config.mk](https://android.googlesource.com/platform/build/+/main/core/config…
326 _not_ build the entire tree; just the minimum number of projects that are
365 Currently, the list of bionic CTS tests is generated at build time by
415 To get test coverage for bionic, use `//bionic/build/coverage.sh`. Before
/bionic/benchmarks/
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
/bionic/tools/versioner/src/
DAndroid.bp8 defaults: ["llvm-build-host-tools-defaults"],
/bionic/tests/
Drun-on-host.sh3 . $(dirname $0)/../build/run-on-host.sh
DAndroid.bp1229 // Clang cannot build ifunc with LTO.
/bionic/build/
Drun-on-host.sh3 source ${ANDROID_BUILD_TOP}/build/envsetup.sh
/bionic/libc/kernel/uapi/linux/
Dpsp-sev.h66 __u8 build; member
/bionic/libc/kernel/
DREADME.md111 After this, you will need to build/test the tree to make sure that these
/bionic/docs/
Dstatus.md414 The Android platform is built with `-D_FORTIFY_SOURCE=2`. Users of ndk-build
416 newer. Users of other build systems
418 whatever build system they're using. The exact subset of FORTIFY available to
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
/bionic/linker/
DAndroid.bp348 // when stl is not set to "none" build system adds libdl
/bionic/libc/
DAndroid.bp1320 // to avoid infinite recursion. For the other architectures we just build an
1833 // The build system generally requires that any dependencies of a target
/bionic/libc/malloc_debug/
DREADME.md620 The new line fingerprint line is the contents of the ro.build.fingerprint