Lines Matching full:directory
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
308 #. Create an application directory.
318 Building Zephyr or creating an application in a directory with spaces
336 #. Place your application source code in the :file:`src` sub-directory. For
339 #. Create a file named :file:`CMakeLists.txt` in the ``app`` directory with the
515 create a :file:`Kconfig` file in the same directory as your
543 the application directory, but it is also possible for it to be
610 .. _application-configuration-directory:
612 Application Configuration Directory
616 directory except for files with an absolute path provided by the arguments
620 The application configuration directory is defined by the
629 configuration directory.
631 2. The application's source directory.
639 application directory. For example, C++ support could be enabled with this
735 application's :file:`src` directory. If the application adds a large
748 directory but it is important that both application and library code targets
833 #. Navigate to the application directory :file:`<app>`.
863 .. _build-directory-contents:
865 Build Directory Contents
868 When using the Ninja generator a build directory looks like this:
880 The most notable files in the build directory are:
884 * A :file:`zephyr` directory, which is the working directory of the
889 the :file:`zephyr` sub-directory of the build directory. (This is **not the
890 Zephyr base directory**, which contains the Zephyr source code etc. and is
932 build directory :file:`<app>/build`.
979 duplicating all the files described in :ref:`create-your-board-directory` for
1024 #. Run one of these console commands from the build directory,
1077 #. Run one of these console commands from the build directory,
1139 where the ``boards`` directory hosts the board you are building for:
1152 and the ``soc`` directory hosts any SOC code. You can also have boards that are
1193 Zephyr binary into your application directory.
1204 be used. Relative paths are treated relatively to the application directory.
1273 Zephyr binary into your application directory.
1287 used. Relative paths are treated relatively to the application directory.
1294 Devicetree directory trees are found in ``APPLICATION_SOURCE_DIR``,
1296 can be added by creating this directory tree::
1304 Where 'arm' is changed to the appropriate architecture. Each directory
1305 is optional. The binding directory contains bindings and the other
1308 Once the directory structure is in place, you can use it by specifying
1327 used. Relative paths are treated relatively to the application directory.
1330 include files that can be located in a ``DTS_ROOT`` directory. By