| /hardware/bsp/intel/peripheral/libupm/doxy/node/ |
| D | tolower.js | 58 function getHtmlFilenames (directory) argument
60 return fs.readdirSync(directory).map(function (file) {
61 return path.join(directory, file);
77 var directory = path.dirname(file);
80 fs.renameSync(file, directory + "/" + newFileName); //, function(err)
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/test/ |
| D | tools_common.sh | 333 --bin-path <path to libvpx binaries directory>
334 --config-path <path to libvpx config directory>
338 --test-data-path <path to libvpx test data directory>
342 \$LIBVPX_BIN_PATH and then the current directory.
345 \$LIBVPX_CONFIG_PATH and then the current directory.
348 \$LIBVPX_TEST_DATA_PATH and then the current directory.
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/nestegg/ |
| D | INSTALL | 4 0. Change directory into the source directory.
|
| D | README | 5 The source under the halloc/ directory is licensed under a BSD license. See
|
| D | README.webm | 7 The source under the halloc/ directory is licensed under a BSD license. See
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/build/x86-msvs/ |
| D | obj_int_extract.bat | 11 REM %1 - Relative path to the directory containing the vp8 source directory.
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/test/android/ |
| D | README | 2 1) Configure libvpx from the parent directory:
8 2) From the parent directory, invoke ndk-build:
|
| /hardware/intel/common/libmix/mix_common/ |
| D | INSTALL | 20 those values to create a `Makefile' in each directory of the package.
47 1. `cd' to the directory containing the package's source code and type
62 source code directory by typing `make clean'. To also remove the
93 own directory. To do this, you can use GNU `make'. `cd' to the
94 directory where you want the object files and executables to go and run
96 source code in the directory that `configure' is in and in `..'.
99 architecture at a time in the source code directory. After you have
131 In addition, if you use an unusual directory layout you can give
276 Look for the package's source code in directory DIR. Usually
277 `configure' can determine that directory automatically.
|
| D | ChangeLog | 8 * Fixed inclusion of m4 directory.
|
| /hardware/bsp/intel/peripheral/libmraa/src/python/docs/ |
| D | CMakeLists.txt | 18 # HTML output directory
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/build/arm-msvs/ |
| D | obj_int_extract.bat | 11 REM %1 - Relative path to the directory containing the vp8 and vpx_scale
|
| /hardware/bsp/intel/peripheral/libmraa/src/pwm/ |
| D | pwm.c | 253 char directory[MAX_SIZE]; in mraa_pwm_init_raw() local
254 snprintf(directory, MAX_SIZE, SYSFS_PWM "/pwmchip%d/pwm%d", dev->chipid, dev->pin); in mraa_pwm_init_raw()
256 if (stat(directory, &dir) == 0 && S_ISDIR(dir.st_mode)) { in mraa_pwm_init_raw()
|
| /hardware/libhardware/tests/vehicle/ |
| D | README | 44 You can build everything by issuing the following from the top of directory. It
63 target device. You can load it anywhere in your /data directory and run it as:
|
| /hardware/bsp/intel/peripheral/libupm/docs/ |
| D | building.md | 6 directory.
81 you're in the build directory, to make the lcd module you would:
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/googletest/src/ |
| D | README | 91 prefer for that type. This will result in a new directory with the
116 Suppose you put Google Test in directory ${GTEST_DIR}. To build it,
139 As an example, the make/ directory contains a Makefile that you can
168 mkdir mybuild # Create a directory to hold the build output.
178 current directory. Just type 'make' to build gtest.
210 end up in your selected build directory (selected in the Xcode
416 gtest-type-util.h in the same directory.
421 regenerate them. You can find pump.py in the scripts/ directory.
|
| /hardware/bsp/intel/peripheral/libmraa/cmake/modules/ |
| D | FindFtd2xx.cmake | 5 # LIBFTD2XX_INCLUDE_DIRS - the libftd2xx include directory
|
| D | FindFtd4222.cmake | 5 # LIBFT4222_INCLUDE_DIRS - the LIBFT4222 include directory
|
| /hardware/bsp/intel/peripheral/sensors/mraa/doc/ |
| D | Doxyfile | 52 # to the output directory.
59 # left blank the current directory will be used.
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
150 # If left blank the directory from which doxygen is run is used as the path to
154 # will be relative from the directory where doxygen is started.
670 # Note that if you run doxygen from a directory containing a file called
754 # Note: If this tag is empty the current directory is searched.
827 # subdirectory from a directory tree whose root is specified with the INPUT tag.
829 # Note that relative paths are relative to the directory from which doxygen is
[all …]
|
| /hardware/bsp/intel/peripheral/libupm/doxy/ |
| D | Doxyfile.in | 52 # to the output directory.
59 # left blank the current directory will be used.
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
152 # If left blank the directory from which doxygen is run is used as the path to
156 # will be relative from the directory where doxygen is started.
681 # Note that if you run doxygen from a directory containing a file called
765 # Note: If this tag is empty the current directory is searched.
841 # subdirectory from a directory tree whose root is specified with the INPUT tag.
843 # Note that relative paths are relative to the directory from which doxygen is
[all …]
|
| D | Doxyfile.java.in | 52 # to the output directory.
59 # left blank the current directory will be used.
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
152 # If left blank the directory from which doxygen is run is used as the path to
156 # will be relative from the directory where doxygen is started.
681 # Note that if you run doxygen from a directory containing a file called
765 # Note: If this tag is empty the current directory is searched.
801 # subdirectory from a directory tree whose root is specified with the INPUT tag.
803 # Note that relative paths are relative to the directory from which doxygen is
[all …]
|
| /hardware/bsp/intel/peripheral/libmraa/ |
| D | Doxyfile.java.in | 52 # to the output directory.
59 # left blank the current directory will be used.
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
150 # If left blank the directory from which doxygen is run is used as the path to
154 # will be relative from the directory where doxygen is started.
670 # Note that if you run doxygen from a directory containing a file called
754 # Note: If this tag is empty the current directory is searched.
794 # subdirectory from a directory tree whose root is specified with the INPUT tag.
796 # Note that relative paths are relative to the directory from which doxygen is
[all …]
|
| D | Doxyfile.in | 52 # to the output directory.
59 # left blank the current directory will be used.
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
150 # If left blank the directory from which doxygen is run is used as the path to
154 # will be relative from the directory where doxygen is started.
670 # Note that if you run doxygen from a directory containing a file called
754 # Note: If this tag is empty the current directory is searched.
829 # subdirectory from a directory tree whose root is specified with the INPUT tag.
831 # Note that relative paths are relative to the directory from which doxygen is
[all …]
|
| /hardware/intel/common/libva/doc/ |
| D | Doxyfile | 43 # Doxygen will copy the logo to the output directory.
50 # where doxygen was started. If left blank the current directory will be used.
55 # 4096 sub-directories (in 2 levels) under the output directory of each output
58 # source files, where putting all generated files in the same directory would
125 # If left blank the directory from which doxygen is run is used as the
504 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
629 # subdirectory from a directory tree whose root is specified with the INPUT tag.
833 # the style sheet file to the HTML output directory, so don't put your own
834 # stylesheet in the HTML output directory as well, or it will be erased!
887 # HTML output directory. Running make will produce the docset in that
[all …]
|
| /hardware/bsp/intel/peripheral/libmraa/docs/ |
| D | building.md | 6 directory inside the clone directory.
150 Have JAVA_HOME set to JDK install directory. Most distributions set this from `/etc/profile.d/`
|
| /hardware/bsp/intel/peripheral/libmraa/src/gpio/ |
| D | gpio.c | 97 char directory[MAX_SIZE]; in mraa_gpio_init_internal() local
98 snprintf(directory, MAX_SIZE, SYSFS_CLASS_GPIO "/gpio%d/", dev->pin); in mraa_gpio_init_internal()
100 if (stat(directory, &dir) == 0 && S_ISDIR(dir.st_mode)) { in mraa_gpio_init_internal()
|