Lines Matching refs:will
91 Once an application has been defined, you will use CMake to generate a **build
265 This will create a new workspace with the :ref:`T2 topology <west-t2>`, with
270 repository will match the example-application's contents when you clone it. You
282 and your workspace will be ready for use.
320 :file:`C:\\Users\\YourName\\app` will work, but
321 :file:`C:\\Users\\Your Name\\app` will not.
354 invoked by the Zephyr package on the next line. CMake will error out if
360 target is how you include them in the build. The Zephyr package will
406 ``find_package(Zephyr)`` will automatically set this as a cached CMake
411 will use for the default configuration. See :ref:`boards` for
443 system will not automatically pick up any modules from west.
446 will be added to the list of modules found via west, instead of replacing it.
448 * :makevar:`FILE_SUFFIX`: Optional suffix for filenames that will be added to Kconfig
449 fragments and devicetree overlays (if these files exists, otherwise will fallback to
487 ``west build``) using ``-DBOARD=YOUR_BOARD`` will be checked for and
491 will then be used.
494 as described in this step, this value will be used.
615 Zephyr will use configuration files from the application's configuration
623 ``APPLICATION_CONFIG_DIR`` will be set by one of the sources below with the
663 are still in early stages of their development cycle. Such features will be
674 :kconfig:option:`CONFIG_WARN_EXPERIMENTAL` will print the following warning at
696 files without these suffixes will be used instead.
713 ``prj.conf`` and ``boards/native_sim.overlay`` will be used.
716 ``prj.conf`` will be used, no application devicetree overlay will be used.
719 ``prj_mouse.conf`` and ``boards/native_sim.overlay`` will be used (there is no
723 ``prj_mouse.conf`` will be used and ``boards/qemu_cortex_m3_mouse.overlay`` will be used.
727 When ``CONF_FILE`` is set in the form of ``prj_X.conf`` then the ``X`` will be used as the
728 build type. If this is combined with ``FILE_SUFFIX`` then the file suffix option will take
760 The following variables will often need to be exported to the
785 will use in the second stage.
797 For simplicity we will use ``ninja`` throughout this guide, and if you
798 choose to use ``west build`` to build your application know that it will
845 parameter. These settings will override the settings in the application's
888 After running ``ninja``, the following build output files will be written to
995 When targeting a board revision, the active revision will be printed at CMake
1103 target will use the SDK's QEMU binary by default. To use another version of
1124 this structure, it will be much easier to upstream your platform related work into
1163 will be needed when submitting to Zephyr.
1192 This will use your custom board configuration and will generate the
1221 The file :zephyr_file:`soc/Kconfig` will create the top-level
1272 This will use your custom platform configurations and will generate the