Searched refs:path (Results 1 – 11 of 11) sorted by relevance
/chre-3.4.0/chpp/api_parser/ |
D | chre_api_to_chpp.py | 20 import os.path 51 script_dir = os.path.dirname(os.path.realpath(__file__)) 53 chre_project_base_dir = os.path.normpath(script_dir + "/../..") 79 os.path.basename(__file__))) 97 clang_format_path = os.path.normpath( 834 output_file = os.path.join(system_chre_abs_path(), CHPP_PARSER_INCLUDE_PATH, filename) 870 output_file = os.path.join(system_chre_abs_path(), CHPP_PARSER_SOURCE_PATH, filename) 934 return [os.path.join(chre_project_base_dir, file) for file in files]
|
D | README.md | 66 on all fields and placing the optimized path in an if/else condition, the 67 compiler can evaluate condition 1 and prune away code for the less-optimal path.
|
/chre-3.4.0/host/common/test/ |
D | chre_test_client.cc | 340 const std::string path{argi < argc ? argv[argi++] : ""}; in main() local 350 if (idstr.empty() || path.empty()) { in main() 365 sendLoadNanoappRequest(client, path.c_str(), id, appVersion, apiVersion, in main()
|
/chre-3.4.0/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 138 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path 140 # shortest path that makes the file name unique will be used 145 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. 147 # part of the path. The tag can be used to show relative paths in the file list. 148 # If left blank the directory from which doxygen is run is used as the path to 158 # path mentioned in the documentation of a class, which tells the reader which 695 # search path. See also \cite for info how to create references. 827 # Note that the wildcards are matched against the file with absolute path, so to [all …]
|
/chre-3.4.0/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 138 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path 140 # shortest path that makes the file name unique will be used 145 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. 147 # part of the path. The tag can be used to show relative paths in the file list. 148 # If left blank the directory from which doxygen is run is used as the path to 158 # path mentioned in the documentation of a class, which tells the reader which 695 # search path. See also \cite for info how to create references. 827 # Note that the wildcards are matched against the file with absolute path, so to [all …]
|
/chre-3.4.0/doc/ |
D | framework_testing.md | 14 machine, only components that are OS independent can be tested via this path.
|
D | framework_overview.md | 40 path this takes can vary, one common approach is to transmit the binary into 169 appropriate include path and source files. This includes the path used to
|
D | nanoapp_overview.md | 93 This path is most commonly used to deploy nanoapps to production, as the entire
|
D | nanoapp_developer_guide.md | 197 `NANOPB_PREFIX` environment variable to its path
|
/chre-3.4.0/chpp/ |
D | README.md | 138 …terface between the CHPP Transport layer and the communications link’s Rx path (e.g. from the UART… 148 …terface between the CHPP Transport layer and the communications link’s Tx path (e.g. to the UART d…
|
/chre-3.4.0/build/sys_support/qcom/ |
D | chre.scons | 247 # Define path to the IDL file used to communicate with the host via FastRPC
|