Home
last modified time | relevance | path

Searched refs:paths (Results 1 – 13 of 13) sorted by relevance

/hardware/libhardware_legacy/power/
Dpower.c53 open_file_descriptors(const char * const paths[]) in open_file_descriptors() argument
57 int fd = open(paths[i], O_RDWR | O_CLOEXEC); in open_file_descriptors()
60 fprintf(stderr, "fatal error opening \"%s\": %s\n", paths[i], in open_file_descriptors()
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/nestegg/
DREADME.webm12 - nestegg/0001-include-paths.diff
/hardware/bsp/intel/peripheral/libmraa/docs/
Dbuilding.md49 See flags for adjusting install paths in the section below.
51 Currently our install logic puts Python bindings into standard paths, which
53 [policy](http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths).
/hardware/bsp/intel/peripheral/libupm/docs/
Dbuilding.md9 following environment variables to configure the paths:
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/build/make/
Dgen_msvs_proj.sh40 -Lpath/to/lib Additional library search paths
Dgen_msvs_vcxproj.sh41 -Lpath/to/lib Additional library search paths
/hardware/bsp/intel/peripheral/sensors/mraa/doc/
DDoxyfile149 # part of the path. The tag can be used to show relative paths in the file list.
153 # Note that you can specify absolute paths here, but also relative paths, which
163 # specify the list of include paths that are normally passed to the compiler
829 # Note that relative paths are relative to the directory from which doxygen is
2020 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
/hardware/bsp/intel/peripheral/libupm/doxy/
DDoxyfile.in151 # part of the path. The tag can be used to show relative paths in the file list.
155 # Note that you can specify absolute paths here, but also relative paths, which
165 # specify the list of include paths that are normally passed to the compiler
843 # Note that relative paths are relative to the directory from which doxygen is
2036 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
DDoxyfile.java.in151 # part of the path. The tag can be used to show relative paths in the file list.
155 # Note that you can specify absolute paths here, but also relative paths, which
165 # specify the list of include paths that are normally passed to the compiler
803 # Note that relative paths are relative to the directory from which doxygen is
1998 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
/hardware/bsp/intel/peripheral/libmraa/
DDoxyfile.java.in149 # part of the path. The tag can be used to show relative paths in the file list.
153 # Note that you can specify absolute paths here, but also relative paths, which
163 # specify the list of include paths that are normally passed to the compiler
796 # Note that relative paths are relative to the directory from which doxygen is
1989 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
DDoxyfile.in149 # part of the path. The tag can be used to show relative paths in the file list.
153 # Note that you can specify absolute paths here, but also relative paths, which
163 # specify the list of include paths that are normally passed to the compiler
831 # Note that relative paths are relative to the directory from which doxygen is
2012 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/
Dlibs.doxy_template117 # the path. The tag can be used to show relative paths in the file list.
127 # definition is used. Otherwise one should specify the include paths that
1099 # where "loc1" and "loc2" can be relative or absolute paths or
/hardware/intel/common/libva/doc/
DDoxyfile124 # the path. The tag can be used to show relative paths in the file list.
134 # definition is used. Otherwise one should specify the include paths that
1443 # where "loc1" and "loc2" can be relative or absolute paths or