Searched refs:relative (Results 1 – 19 of 19) sorted by relevance
/system/core/bootstat/ |
D | README.md | 4 `boot_complete`) and the relative time at which these events occurred. The 24 To record the relative time of an event during the boot phase, call `bootstat` 29 The relative time at which the command runs is recorded along with the name of
|
/system/extras/simpleperf/demo/SimpleperfExampleWithNative/app/ |
D | CMakeLists.txt | 9 # or SHARED, and provides the relative paths to its source code. 19 # Provides a relative path to your source file(s).
|
/system/chre/build/variant/ |
D | qcom_hexagonv60_nanohub-uimg.mk | 9 TARGET_CFLAGS += -mno-pic-data-is-text-relative
|
D | google_hexagonv62_slpi-uimg.mk | 12 TARGET_CFLAGS += -mno-pic-data-is-text-relative
|
/system/update_engine/ |
D | .clang-format | 18 # style guide defined by Brillo. To use this file create a *relative* symlink in
|
D | update_metadata.proto | 231 // relative to the root of this filesystem. If not set, the default "postinst"
|
/system/tools/hidl/ |
D | Coordinator.h | 104 status_t getPackagePath(const FQName& fqName, bool relative, bool sanitized,
|
D | Coordinator.cpp | 418 status_t Coordinator::getPackagePath(const FQName& fqName, bool relative, bool sanitized, in getPackagePath() argument 432 if (!relative) { in getPackagePath()
|
/system/tools/aidl/docs/ |
D | aidl-cpp.md | 52 need to add a path to `LOCAL_AIDL_INCLUDES`. This path should be relative to 71 binary or java), just add a relative path to the .aidl files to 73 in other directory hierarchies: add the include root path relative to the
|
/system/libufdt/utils/ |
D | README.md | 96 the DTB/DTBO file and assign into relative property in `dt_table_entry`.
|
/system/media/audio_utils/ |
D | Doxyfile | 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 139 # part of the path. The tag can be used to show relative paths in the file list. 143 # Note that you can specify absolute paths here, but also relative paths, which 144 # will be relative from the directory where doxygen is started. 778 # Note that relative paths are relative to the directory from which doxygen is 1006 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1256 # the file name of the resulting .qch file. The path specified is relative to 1422 # When MathJax is enabled you need to specify the location relative to the HTML [all …]
|
D | Doxyfile.orig | 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 139 # part of the path. The tag can be used to show relative paths in the file list. 143 # Note that you can specify absolute paths here, but also relative paths, which 144 # will be relative from the directory where doxygen is started. 778 # Note that relative paths are relative to the directory from which doxygen is 1006 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1256 # the file name of the resulting .qch file. The path specified is relative to 1422 # When MathJax is enabled you need to specify the location relative to the HTML [all …]
|
/system/chre/build/sys_support/qcom/ |
D | uimage.lcs.toolv80 | 187 Symbols in the DWARF debugging sections are relative to the beginning
|
/system/chre/pal/doc/ |
D | Doxyfile | 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 147 # part of the path. The tag can be used to show relative paths in the file list. 151 # Note that you can specify absolute paths here, but also relative paths, which 152 # will be relative from the directory where doxygen is started. 811 # Note that relative paths are relative to the directory from which doxygen is 1047 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1301 # the file name of the resulting .qch file. The path specified is relative to 1467 # When MathJax is enabled you need to specify the location relative to the HTML [all …]
|
/system/chre/chre_api/doc/ |
D | Doxyfile | 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 57 # into which the generated documentation will be written. If a relative path is 58 # entered, it will be relative to the location where doxygen was started. If 147 # part of the path. The tag can be used to show relative paths in the file list. 151 # Note that you can specify absolute paths here, but also relative paths, which 152 # will be relative from the directory where doxygen is started. 811 # Note that relative paths are relative to the directory from which doxygen is 1047 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1301 # the file name of the resulting .qch file. The path specified is relative to 1467 # When MathJax is enabled you need to specify the location relative to the HTML [all …]
|
/system/chre/ |
D | README.md | 222 be avoided, due to the relative scarcity of memory and CPU resources, and
|
/system/core/libutils/ |
D | README | 238 idmap-magic constant spells "idmp" in ASCII. Offsets are given relative
|
/system/core/adb/ |
D | protocol.txt | 50 The identifiers "local-id" and "remote-id" are always relative to the
|
/system/update_engine/update_engine/ |
D | update_metadata.proto | 231 // relative to the root of this filesystem. If not set, the default "postinst"
|