Searched refs:built (Results 1 – 25 of 37) sorted by relevance
12
/system/tools/xsdc/ |
D | README.md | 100 values: built-in data type, simpleType or complexType 118 values: built-in data type, simpleType or complexType 139 values: built-in data type 145 values: built-in data type, simpleType or complexType 157 values: built-in data type, or simpleType 163 values: built-in data type, or simpleType 178 values: built-in data type
|
/system/chre/host/msm/daemon/ |
D | README.md | 4 This daemon cannot be built out of this folder, however, because it depends on
|
/system/core/libstats/socket/ |
D | stats_event.c | 48 bool built; member 65 event->built = false; in stats_event_obtain() 304 if (event->built) return; in stats_event_build() 327 event->built = true; in stats_event_build()
|
/system/bt/gd/ |
D | README.md | 14 Gabeldorsche (GD) was built with test driven development in mind. Three types of
|
/system/extras/simpleperf/demo/SimpleperfExampleWithNative/app/ |
D | profiling.gradle | 16 // Exclude wrap.sh for architectures not built.
|
/system/extras/simpleperf/demo/SimpleperfExampleOfKotlin/app/ |
D | profiling.gradle | 17 // Exclude wrap.sh for architectures not built.
|
/system/extras/simpleperf/demo/SimpleperfExamplePureJava/app/ |
D | profiling.gradle | 17 // Exclude wrap.sh for architectures not built.
|
/system/core/libprocessgroup/cgrouprc/ |
D | Android.bp | 22 // defined below. The static library is built for tests.
|
/system/core/trusty/gatekeeper/ |
D | Android.bp | 16 // WARNING: Everything listed here will be built on ALL platforms,
|
/system/core/trusty/confirmationui/ |
D | Android.bp | 16 // WARNING: Everything listed here will be built on ALL platforms,
|
/system/apex/docs/ |
D | README.md | 72 that signs the same APEX in the built-in partitions. 152 ### APEX in built-in partitions 154 APEX files can be located in built-in partitions such as `/system`. The 159 If an APEX is present in a built-in partition, the APEX can be updated by 162 shadows the version already present in the built-in partition. But unlike APKs, 506 kernel to fully support APEX. For example, the kernel might have been built 510 Flattened APEX is a specially built APEX that can be activated on devices with 512 under the built-in partition. For example, `lib/libFoo.so` in a flattend APEX 529 like Mainline. APEXes that are not pre-signed (i.e. built from the source) 552 The files in an APEX container are from built-in partitions (for example, the
|
/system/apex/shim/ |
D | README.md | 50 Shim apex files should be built on a build server and then downloaded from it
|
/system/bt/service/ |
D | Android.bp | 59 // Main unit test sources. These get built for host and target.
|
/system/sepolicy/prebuilts/api/26.0/private/ |
D | seapp_contexts | 63 # rules are never output to the built seapp_contexts file. Like all keywords,
|
/system/sepolicy/prebuilts/api/27.0/private/ |
D | seapp_contexts | 63 # rules are never output to the built seapp_contexts file. Like all keywords,
|
/system/extras/simpleperf/doc/ |
D | README.md | 52 system libraries are built with .gnu_debugdata section starting from Android O. 244 If built successfully, out/target/product/generic_arm64/system/bin/simpleperf is for ARM64, and
|
/system/chre/build/sys_support/qcom/ |
D | chre.scons | 244 # Setup source files to be built 366 # Add CHRE as a shared library that should be built
|
/system/sepolicy/prebuilts/api/28.0/private/ |
D | seapp_contexts | 63 # rules are never output to the built seapp_contexts file. Like all keywords,
|
/system/sepolicy/public/ |
D | netd.te | 171 # (things it requires should be built directly into the kernel)
|
/system/sepolicy/prebuilts/api/30.0/public/ |
D | netd.te | 182 # (things it requires should be built directly into the kernel)
|
/system/sepolicy/prebuilts/api/29.0/private/ |
D | seapp_contexts | 103 # rules are never output to the built seapp_contexts file. Like all keywords,
|
/system/core/init/ |
D | README.ueventd.md | 5 built on the same parser as init.
|
/system/sepolicy/private/ |
D | seapp_contexts | 103 # rules are never output to the built seapp_contexts file. Like all keywords,
|
/system/chre/ |
D | README.md | 154 All nanoapps in the ``apps`` directory are placed in a namespace when built
|
/system/sepolicy/prebuilts/api/30.0/private/ |
D | seapp_contexts | 103 # rules are never output to the built seapp_contexts file. Like all keywords,
|
12