Searched refs:directory (Results 1 – 25 of 320) sorted by relevance
12345678910>>...13
| /Zephyr-Core-3.5.0/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-Core-3.5.0/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 | 28 # - BOARD_DIR: directory containing the board definition (added to DTS_ROOT)
36 # source directory.
39 # DTS_ROOT always includes the application directory, the board
40 # directory, shield directories, and ZEPHYR_BASE.
|
| D | arch.cmake | 5 # Configure ARCH settings based on board directory and arch root.
8 # on board directory and arch root.
21 # - BOARD_DIR: CMake variable specifying the directory of the selected BOARD
|
| /Zephyr-Core-3.5.0/include/zephyr/arch/posix/ |
| D | linker.ld | 26 /* Located in generated directory. This file is populated by the
36 /* Located in generated directory. This file is populated by the
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
69 /* Located in generated directory. This file is populated by the
75 /* Located in generated directory. This file is populated by the
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/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"
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/include/zephyr/arch/sparc/ |
| D | linker.ld | 55 /* Located in generated directory. This file is populated by the
94 /* Located in generated directory. This file is populated by the
107 /* Located in generated directory. This file is populated by the
112 /* Located in generated directory. This file is populated by the
148 /* Located in generated directory. This file is populated by the
157 /* Located in generated directory. This file is populated by the
|
| /Zephyr-Core-3.5.0/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 …]
|
| D | troubleshooting.rst | 27 …ifest: running 'git fetch ... https://github.com/your-username/your_project ...' in /some/directory
48 environment variable does not contain the directory where pip installed
55 You need to find the directory containing :file:`west.exe`, then add it to your
69 #. Look for a file named ``west.exe`` in the ``scripts`` directory
76 #. If you see ``west.exe`` in the ``scripts`` directory, add the full path to
81 **Do not just copy/paste this command**. The ``scripts`` directory location
149 directory you created when you :ref:`got started <getting_started>`).
151 For example, create your build directory inside the workspace, or run ``west
202 #. Completely remove the :file:`zephyrproject/.west` directory (if you don't,
214 FATAL ERROR: already in an installation (<some directory>), aborting
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/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-Core-3.5.0/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-Core-3.5.0/include/zephyr/arch/mips/ |
| D | linker.ld | 88 /* Located in generated directory. This file is populated by the
122 /* Located in generated directory. This file is populated by the
131 /* Located in generated directory. This file is populated by the
136 /* Located in generated directory. This file is populated by the
175 /* Located in generated directory. This file is populated by the
184 /* Located in generated directory. This file is populated by the
|
| /Zephyr-Core-3.5.0/samples/subsys/shell/fs/ |
| D | README.rst | 23 Before starting a build, make sure that the i386 pkgconfig directory is in your
137 Change current working directory to given path
146 List current working directory
183 Create a directory
192 Remove a file or directory
204 By default the flash partitions are accessible through the directory *flash*
205 relative to the directory where the build is started.
|
| /Zephyr-Core-3.5.0/scripts/west_commands/tests/nrf/ |
| D | README.rst | 1 This directory contains test data files for test_nrf.py.
|
| /Zephyr-Core-3.5.0/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…
|
| D | zephyr_sdk.rst | 45 directory.
47 You can also set :envvar:`ZEPHYR_SDK_INSTALL_DIR` to point to a directory
92 cd <sdk download directory>
105 If you want to uninstall the SDK, remove the directory where you installed it.
106 If you relocate the SDK directory, you need to re-run the setup script.
119 The Zephyr SDK bundle archive contains the ``zephyr-sdk-0.16.3`` directory and, when
156 The Zephyr SDK bundle archive contains the ``zephyr-sdk-0.16.3`` directory and, when
170 You must rerun the setup script if you relocate the Zephyr SDK bundle directory after
200 The Zephyr SDK bundle archive contains the ``zephyr-sdk-0.16.3`` directory and, when
214 You must rerun the setup script if you relocate the Zephyr SDK bundle directory after
|
| D | other_x_compilers.rst | 36 toolchain's binaries have, e.g. the path to the directory containing the
54 directory and have a common file name prefix. The ``CROSS_COMPILE`` variable
55 is set to the directory concatenated with the file name prefix. In the Debian
57 ``arm-none-eabi-gcc`` and ``arm-none-eabi-ld`` in directory ``/usr/bin/``, so
|
| /Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/test-bindings-include/ |
| D | README.rst | 1 This directory contains bindings used to test the 'include:' feature.
|
| /Zephyr-Core-3.5.0/soc/riscv/openisa_rv32m1/ |
| D | linker.ld | 106 /* Located in generated directory. This file is populated by calling
135 /* Located in generated directory. This file is populated by the
176 /* Located in generated directory. This file is populated by the
190 /* Located in generated directory. This file is populated by the
224 /* Located in generated directory. This file is populated by the
231 /* Located in generated directory. This file is populated by the
236 /* Located in generated directory. This file is populated by the
|
12345678910>>...13
