| /Zephyr-latest/scripts/build/ |
| D | subfolder_list.py | 6 This script will walk the specified directory and write the file specified with
24 parser.add_argument('-d', '--directory', required=True,
25 help='Directory to walk for sub-directory discovery')
27 help='Create links for each directory found in \
28 directory given')
40 def get_subfolder_list(directory, create_links=None): argument
41 """Return subfolder list of a directory"""
47 symbase = os.path.basename(directory)
50 os.symlink(directory, symlink)
53 dirlist.append(directory)
[all …]
|
| /Zephyr-latest/subsys/bluetooth/services/ots/ |
| D | ots_dir_list_internal.h | 19 /** Maximum size of the Directory Listing Object Record. Table 4.1 in the OTS spec. */
24 /** @brief Directory Listing Buffer Size
41 /** @brief Directory Listing record flag field. */
63 * @param flags Directory Listing Object flags.
70 * @param flags Directory Listing Object flags.
77 * @param flags Directory Listing Object flags.
84 * @param flags Directory Listing Object flags.
91 * @param flags Directory Listing Object flags.
98 * @param flags Directory Listing Object flags.
105 * @param flags Directory Listing Object flags.
[all …]
|
| D | Kconfig | 18 bool "The Directory Listing Object"
20 Enables the Directory Listing Object, which is an object that contains all the metadata
25 string "The object name of the Directory Listing Object"
26 default "Directory"
29 The name of the Directory Listing Object when it is read by a client.
87 # Given the maximum size of a directory listing record (172) and the maximum size of an
|
| /Zephyr-latest/include/zephyr/fs/ |
| D | fs_sys.h | 97 * @name Directory operations
101 * Opens an existing directory specified by the path.
103 * @param dirp Directory to open.
104 * @param fs_path Path to the directory.
109 * Reads directory entries of an open directory.
111 * @param dirp Directory to read from.
112 * @param entry Next directory entry in the dirp directory.
117 * Closes an open directory.
119 * @param dirp Directory to close.
144 * Deletes the specified file or directory.
[all …]
|
| D | fs.h | 31 * @brief Enumeration for directory entry types
36 /** Identifier for directory entry */
96 /** Mount point directory name (ex: "/fatfs") */
112 * @brief Structure to receive file or directory information
114 * Used in functions that read the directory entries to get
115 * file or directory information.
119 * File/directory type (FS_DIR_ENTRY_FILE or FS_DIR_ENTRY_DIR)
122 /** Name of file or directory */
124 /** Size of file (0 if directory). */
312 * Deletes the specified file or directory
[all …]
|
| /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 | arch_v1.cmake | 9 # Configure ARCH settings based on board directory and arch root.
12 # on board directory and arch root.
20 # - ARCH_DIR: Directory containing the arch implementation.
25 # - BOARD_DIR: CMake variable specifying the directory of the selected BOARD
|
| /Zephyr-latest/scripts/west_commands/ |
| D | build_helpers.py | 21 # Domains.py must be imported from the pylib directory, since
28 '''Name of the default Zephyr build directory.'''
34 If the build directory is not given, the default is {}/ unless the
35 build.dir-fmt configuration variable is set. The current directory is
36 checked after that. If either is a Zephyr build directory, it is used.
85 '''Heuristic for finding a build directory.
87 The default build directory is computed by reading the build.dir-fmt
92 the default build folder is a build directory, it is returned.
93 Next, if the current working directory is a build directory, it is
94 returned. Finally, the default build directory is returned (may be None).
[all …]
|
| D | spdx.py | 39 help="build directory")
43 help="SPDX output directory")
70 self.die("Build directory not specified; call `west spdx --init --build-dir=BUILD_DIR`")
77 self.err("Couldn't create CMake file-based API query directory")
82 self.die("Build directory not specified; call `west spdx --build-dir=BUILD_DIR`")
103 # make sure SPDX directory exists, or create it if it doesn't
106 self.err(f'SPDX output directory {cfg.spdxDir} exists but is not a directory')
108 # directory exists, we're good
110 # create the directory
|
| D | build.py | 46 source_dir application source directory
52 A "pristine" build directory is empty. The -p option controls
53 whether the build directory is made pristine before the build
80 '''Source directory for the build, or None on error.'''
83 '''Final build directory used to run the build, or None on error.'''
86 '''True if the build directory was created; False otherwise.'''
117 help='build directory to create or use')
133 or sample.yaml. If source directory is not used
137 If source directory is passed
214 self.die("source directory specified twice:({} and {})".format(
[all …]
|
| /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/tests/posix/fs/src/ |
| D | test_fs_dir.c | 123 * @details Test creates a new directory through POSIX
124 * mkdir API and open a new file under the directory and
136 * @details Test opens an existing directory through POSIX
137 * opendir API, reads the contents of the directory through
160 * @details Test creates a new directory through POSIX
161 * mkdir API and remove directory using rmdir.
166 /* Create and remove empty directory */ in ZTEST()
170 /* Create directory and open a file in the directory in ZTEST()
171 * now removing the directory will fail, test will in ZTEST()
172 * fail in removal of non empty directory in ZTEST()
|
| /Zephyr-latest/scripts/west_commands/zspdx/ |
| D | sbom.py | 23 # location of build directory
26 # location of SPDX document output directory
38 # 1) build_dir: build directory
40 # check that query dir exists as a directory, or else create it
44 log.err(f'cmake api query directory {cmakeApiDirPath} exists and is not a directory')
46 # directory exists, we're good
48 # create the directory
55 log.err(f'cmake api query file {queryFilePath} exists and is not a directory')
|
| /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/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/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
|
| /Zephyr-latest/subsys/fs/ext2/ |
| D | ext2_impl.h | 155 uint32_t offset; /* (CR, ST, UN) offset of entry in directory */
169 * @retval -ENOTDIR path component not a directory
224 /* Directory operations */
227 * @brief Get directory entry
229 * Reads directory entry that is at offset specified in `ext2_file` structure.
231 * @param dir Read directory
232 * @param ent Directory entry to fill in
240 * @brief Create a directory entry with given attributes
260 * @param parent Parent directory
273 * @brief Create a 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/doc/hardware/arch/ |
| D | x86.rst | 38 at the page directory level, in addition to mapping virtual addresses
40 the entries for identity mapping at the page directory level are
45 is done at the page directory level, there is no need to allocate
47 still be required for additional page directory table.
52 required as the entries in page directory table will be cleared.
58 (Page Directory Pointer) covers 1GB of memory. For example:
71 (Page Directory) covers 4MB of memory.
103 - ``L``: Large page at the page directory level.
|
| /Zephyr-latest/tests/net/all/ |
| D | check_net_options.sh | 8 echo "Usage: $0 <doc build directory>"
10 echo "The parameter needs to point to a directory where Zephyr html"
22 echo "Directory $build_dir not found!"
|
| /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"
|
| /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/doc/develop/application/ |
| D | index.rst | 10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
11 - its **build directory** is :file:`<app>/build`
36 The files in the **application directory** link Zephyr and any modules with the
37 application. This directory contains all application-specific files, such as
55 application files, and links the application directory with Zephyr's CMake
92 directory**, which contains the files you need to build the application and
96 in a separate build directory: Zephyr does not support "in-tree" builds.
236 The directory name :file:`my-app` above is arbitrary: change it as needed. You
237 can now go into this directory and adapt its contents to suit your needs. Since
304 You can follow these steps to create a basic application directory from
[all …]
|
