Searched refs:relative (Results 1 – 25 of 26) sorted by relevance
12
| /system/incremental_delivery/incfs/ |
| D | path.cpp | 170 auto relative = nested.substr(parent.size()); in relativize() local
171 while (relative.front() == '/') { in relativize()
172 relative.remove_prefix(1); in relativize()
174 return relative; in relativize()
|
| /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/linkerconfig/testdata/ |
| D | prepare_root.sh | 109 preinstalled_path=/$(realpath --relative-to=$ROOT_OUT $src)
110 module_path=/$(realpath --relative-to=$ROOT_OUT $dst)
|
| /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/bt/gd/packet/parser/ |
| D | packetgen.gni | 21 # source_root: Root of source relative to current BUILD.gn
98 # source_root: Root of source relative to current BUILD.gn
146 # source_root: Root of source relative to current BUILD.gn
|
| /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 | 256 // relative to the root of this filesystem. If not set, the default "postinst"
|
| /system/extras/perf2cfg/ |
| D | README.md | 7 - Methods are annotated with their contribution relative to the total profile.
9 relative to the method profile.
|
| /system/chre/apps/test/common/proto/ |
| D | chre_cross_validation_sensor.proto | 83 * absolute timestamp instead of the delta relative to the last sample.
|
| /system/tools/hidl/ |
| D | Coordinator.h | 106 status_t getPackagePath(const FQName& fqName, bool relative, bool sanitized,
|
| D | Coordinator.cpp | 415 status_t Coordinator::getPackagePath(const FQName& fqName, bool relative, bool sanitized, in getPackagePath() argument
429 if (!relative) { in getPackagePath()
|
| /system/bt/gd/dumpsys/bundler/ |
| D | bundler.gni | 59 # headers get generated ito subdirectories based on relative path
|
| /system/unwinding/libunwindstack/ |
| D | AndroidVersions.md | 30 FDEs use pc relative addressing in the eh\_frame\_hdr.
114 and uses pc relative FDEs, the unwind will be incorrect. This tends
|
| /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
155 # part of the path. The tag can be used to show relative paths in the file list.
159 # Note that you can specify absolute paths here, but also relative paths, which
160 # will be relative from the directory where doxygen is started.
860 # Note that relative paths are relative to the directory from which doxygen is
1125 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1390 # the file name of the resulting .qch file. The path specified is relative to
1556 # 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/bt/gd/docs/architecture/ |
| D | style_guide.md | 58 * Include path must be relative to the root directory of the stack. Normally
|
| /system/bt/gd/docs/testing/ |
| D | gtest.md | 121 Note: All paths are relative to
|
| /system/chre/doc/ |
| D | framework_overview.md | 194 relative scarcity of memory and CPU resources, and power considerations.
|
| /system/apex/ |
| D | pylintrc | 124 relative-import,
|
| /system/tools/mkbootimg/ |
| D | pylintrc | 118 relative-import,
|
12