Searched refs:directory (Results 1 – 25 of 391) sorted by relevance
12345678910>>...16
| /Zephyr-latest/scripts/build/ |
| D | subfolder_list.py | 28 directory given')
40 def get_subfolder_list(directory, create_links=None): argument
47 symbase = os.path.basename(directory)
50 os.symlink(directory, symlink)
53 dirlist.append(directory)
55 for root, dirs, _ in os.walk(directory, topdown=True):
60 reldir = os.path.relpath(targetdirectory, directory)
111 dirs = get_subfolder_list(args.directory, args.create_links)
|
| /Zephyr-latest/cmake/modules/ |
| D | user_cache.cmake | 5 # Configure user cache directory.
20 # - USER_CACHE_DIR: User cache directory in use.
36 # On macOS, ~/Library/Caches is the preferred cache directory.
69 # The directory is write-able
73 # The directory was not writeable, keep looking for a suitable
74 # directory
79 # Populate local_dir with a suitable directory for caching
80 # files. Prefer a directory outside of the git repository because it
84 # user's cache directory.
93 # Populate USER_CACHE_DIR with a directory that user applications may
|
| D | generated_file_directories.cmake | 5 # This file creates locations in the build directory
11 # - BINARY_DIR_INCLUDE_GENERATED is a directory
|
| D | pre_dt.cmake | 26 # - BOARD_DIR: directory containing the board definition (added to DTS_ROOT)
34 # source directory.
37 # DTS_ROOT always includes the application directory, the board
38 # directory, shield directories, and ZEPHYR_BASE.
|
| /Zephyr-latest/include/zephyr/arch/posix/ |
| D | linker.ld | 30 /* Located in generated directory. This file is populated by the
37 /* Located in generated directory. This file is populated by calling
44 /* Located in generated directory. This file is populated by the
52 /* Located in generated directory. This file is populated by the
60 /* Located in generated directory. This file is populated by the
67 /* Located in generated directory. This file is populated by the
76 /* Located in generated directory. This file is populated by the
82 /* Located in generated directory. This file is populated by the
|
| /Zephyr-latest/submanifests/ |
| D | README.txt | 1 This directory can contain additional west manifest files. Any files
2 in this directory will be included in the main west.yml file sorted by
10 …roject.org/latest/guides/west/manifest.html#example-2-2-downstream-with-directory-of-manifest-files
|
| /Zephyr-latest/include/zephyr/arch/sparc/ |
| D | linker.ld | 49 /* Located in generated directory. This file is populated by calling
63 /* Located in generated directory. This file is populated by the
102 /* Located in generated directory. This file is populated by the
115 /* Located in generated directory. This file is populated by the
120 /* Located in generated directory. This file is populated by the
156 /* Located in generated directory. This file is populated by the
165 /* Located in generated directory. This file is populated by the
|
| /Zephyr-latest/cmake/ |
| D | vif.cmake | 43 " '${board_vif_xml}' in 'boards' directory of application"
44 " directory, or create '${vif_xml}' file in application"
45 " directory or board directory, or supply a custom XML VIF path"
|
| D | llext-edk.cmake | 16 # install directory variable for Makefile.
22 # - ZEPHYR_BASE: Path to the zephyr base directory.
23 # - WEST_TOPDIR: Path to the west top directory.
24 # - APPLICATION_SOURCE_DIR: Path to the application source directory.
25 # - PROJECT_BINARY_DIR: Path to the project binary build directory.
27 # edk directory. This is necessary when building an extension that only
29 # directory.
46 # The generated path is relative to the key directory, and the bindir_out
132 # Use destination parent, as the last part of the source directory is copied as well
151 # Copy syscall headers from edk directory, as they were regenerated there.
|
| /Zephyr-latest/tests/bsim/ |
| D | generate_coverage_report.sh | 47 lcov --capture --directory ${WORK_DIR} --output-file ${OUTPUT_DIR}/coverage.pre.info \
51 genhtml ${OUTPUT_DIR}/coverage.info ${TWISTER_COVERAGE_FILE} --output-directory \
|
| /Zephyr-latest/include/zephyr/arch/mips/ |
| D | linker.ld | 82 /* Located in generated directory. This file is populated by calling
96 /* Located in generated directory. This file is populated by the
130 /* Located in generated directory. This file is populated by the
139 /* Located in generated directory. This file is populated by the
144 /* Located in generated directory. This file is populated by the
183 /* Located in generated directory. This file is populated by the
192 /* Located in generated directory. This file is populated by the
|
| /Zephyr-latest/doc/develop/application/ |
| D | application-kconfig.include | 7 # Sources Kconfig.zephyr in the Zephyr root directory.
9 # Note: All 'source' statements work relative to the Zephyr root directory (due
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 33 - If there is a Zephyr build directory named :file:`build` in your current
34 working directory, it is incrementally re-compiled. The same is true if you
35 run ``west build`` from a Zephyr build directory.
38 directory and no build directory is found, a new one is created and the
45 directory (i.e. the folder containing the application's :file:`CMakeLists.txt`)
59 A build directory named :file:`build` will be created, and the application will
61 that directory. If ``west build`` finds an existing build directory, the
66 build directory; ``west build`` can figure out the board from the CMake cache.
123 To set the application source directory explicitly, give its path as a
126 west build -b <BOARD> path/to/source/directory
[all …]
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | README.md | 5 …located in $ZEPHYR_BASE/scripts/tests directory with all the data files in $ZEPHYR_BASE/scripts/te…
17 The testcases can be executed from the root directory using
49 …rage html report can be generated in every run of "pytest" in the tests directory using configurat…
|
| /Zephyr-latest/ |
| D | .gitignore | 24 # The .cache directory will be used to cache toolchain capabilities if
25 # no suitable out-of-tree directory is found.
69 # Normal west builds will place the Rust target directory under the build directory. However,
|
| /Zephyr-latest/scripts/net/ |
| D | README.txt | 18 * Change working directory to the net-tools repository
31 1. From a Zephyr network sample test directory.
74 directory, which is assumed to be set by the ZEPHYR_BASE environment variable.
75 Should this not be the case, the directory can be set using '-Z' or
78 'docker.conf' exists at the same directory level as the Zephyr base directory.
79 If the net tools are found elsewhere, the net-tools directory can be set with
|
| D | run-sample-tests.sh | 286 $BASENAME [-Z <zephyr base directory>] [-N <net-tools base directory>] [<list of test directories>]
292 set Zephyr base directory
294 set net-tools directory
306 run the tests in these directories instead of current directory
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | db_generation.ecl | 3 # NEEDED: set the variable for the binary output directory from the environment
11 # NEEDED: set the variable for the output directory from the environment
|
| /Zephyr-latest/samples/subsys/shell/fs/ |
| D | README.rst | 32 :file:`flash.bin`, in the current directory to keep the flash content.
48 Before starting a build, make sure that the i386 pkgconfig directory is in your
162 Change current working directory to given path
171 List current working directory
208 Create a directory
217 Remove a file or directory
229 By default the flash partitions are accessible through the directory *flash*
230 relative to the directory where the build is started.
|
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | linker.ld | 110 /* Located in generated directory. This file is populated by calling
128 /* Located in generated directory. This file is populated by calling
143 /* Located in generated directory. This file is populated by the
184 /* Located in generated directory. This file is populated by the
198 /* Located in generated directory. This file is populated by the
232 /* Located in generated directory. This file is populated by the
239 /* Located in generated directory. This file is populated by the
244 /* Located in generated directory. This file is populated by the
|
| /Zephyr-latest/scripts/west_commands/tests/nrf/ |
| D | README.rst | 1 This directory contains test data files for test_nrf.py.
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings-include/ |
| D | README.rst | 1 This directory contains bindings used to test the 'include:' feature.
|
| /Zephyr-latest/soc/sensry/ganymed/sy1xx/common/ |
| D | linker.ld | 103 /* Located in generated directory. This file is populated by calling
134 /* Located in generated directory. This file is populated by the
165 /* Located in generated directory. This file is populated by the
181 /* Located in generated directory. This file is populated by the
215 /* Located in generated directory. This file is populated by the
222 /* Located in generated directory. This file is populated by the
227 /* Located in generated directory. This file is populated by the
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | custom_cmake.rst | 10 - Set ``TOOLCHAIN_ROOT`` to the path to the directory containing your
14 :file:`TOOLCHAIN_ROOT` directory:
61 directory under the directory specified in ``TOOLCHAIN_ROOT`` as
64 :makevar:`USERINCLUDE` can be set to point to the include directory, as shown
|
| D | gnu_arm_embedded.rst | 11 On Windows, we'll assume for this guide that you install into the directory
26 directory.
52 …- Set :envvar:`GNUARMEMB_TOOLCHAIN_PATH` to the brew installation directory (something like ``/usr…
|
12345678910>>...16
