Home
last modified time | relevance | path

Searched +full:ninja +full:- +full:build (Results 1 – 25 of 66) sorted by relevance

123

/Zephyr-latest/doc/develop/west/
Dwithout-west.rst1 .. _no-west:
11 - cloning the additional source code repositories used by Zephyr in
13 - specifying the locations of these repositories to the Zephyr build
15 - flashing and debugging without understanding detailed usage of the
23 .. code-block:: console
27 Otherwise, Zephyr's build system will find it and may try to use
31 ------------------
37 .. code-block:: console
41 git clone https://github.com/zephyrproject-rtos/zephyr
50 ---------------------
[all …]
Dbuild-flash-debug.rst1 .. _west-build-flash-debug:
6 Zephyr provides several :ref:`west extension commands <west-extensions>` for
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
11 commands, see :ref:`flash-and-debug-support` in the board porting guide.
13 .. Add a per-page contents at the top of the page. This page is nested
21 .. _west-building:
23 Building: ``west build``
26 .. tip:: Run ``west build -h`` for a quick overview.
28 The ``build`` command helps you build Zephyr applications from source. You can
29 use :ref:`west config <west-config-cmd>` to configure its behavior.
[all …]
Dsign.rst1 .. _west-sign:
6 The ``west sign`` :ref:`extension <west-extensions>` command can be used to
9 an external, post-processing tool that "stitches" the final components of
10 the image together. Run ``west sign -h`` for command line help.
16 but on :ref:`west config<west-config>`, similar to
17 :ref:`west-building-cmake-config`.
20 flash`` invokes ``west build`` which invokes ``cmake`` and ``ninja`` which invokes
27 difficult. Reproducing a lower ``west sign`` command to debug some build-time issue
28 can be very time-consuming: it requires at least enabling and searching verbose
29 build logs to find which exact options were used. Copying these options from the
[all …]
/Zephyr-latest/doc/contribute/documentation/
Dgeneration.rst11 .. _documentation-overview:
18 using Sphinx to create a formatted stand-alone website. Developers can
36 * Doxygen-generated material used to create all API-specific documents
39 * Script-generated material for kernel configuration options based on Kconfig
43 :caption: Schematic of the documentation build process
51 rtd [shape="rectangle" label="read-the-docs\ntheme"]
56 images -> sphinx
57 rst -> sphinx
58 conf -> sphinx
59 header -> doxygen
[all …]
/Zephyr-latest/samples/tfm_integration/tfm_ipc/
DREADME.rst1 .. zephyr:code-sample:: tfm_ipc
2 :name: TF-M IPC
4 Implement communication between the secure and non-secure images using IPC.
9 This is a simple TF-M integration example that can be used with an ARMv8-M
12 It uses **IPC Mode** for communication, where TF-M API calls are made to the
16 Zephyr uses Trusted Firmware (TF-M) Platform Security Architecture (PSA) APIs
18 non-secure configuration.
20 The sample prints test info to the console either as a single-thread or
21 multi-thread application.
23 The sample reboots after 5 seconds to demonstrate rebooting with TF-M.
[all …]
/Zephyr-latest/tests/arch/arm/arm_no_multithreading/
DREADME.txt1 Title: Test to verify the no multithreading use-case (ARM Only)
5 This test verifies that a Zephyr build without multithreading
7 ARM Cortex-M targets. In detail the test verifies that
8 - system boots to main()
9 - PSP points to the main stack
10 - PSPLIM is set to the main stack base (if applicable)
11 - FPU state is reset (if applicable)
12 - Interrupts are enabled when switching to main()
13 - Interrupts may be registered and serviced
14 - Activating PendSV triggers a Reserved Exception error
[all …]
/Zephyr-latest/doc/_extensions/zephyr/
Dapplication.py3 # SPDX-License-Identifier: Apache-2.0
21 of the shell commands needed to manage (build, flash, etc.) an application.
30 'zephyr-app': directives.unchanged,
31 'cd-into': directives.flag,
33 'host-os': directives.unchanged,
37 'gen-args': directives.unchanged,
38 'build-args': directives.unchanged,
40 'build-dir': directives.unchanged,
41 'build-dir-fmt': directives.unchanged,
43 'maybe-skip-config': directives.flag,
[all …]
/Zephyr-latest/doc/develop/application/
Dindex.rst10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
11 - its **build directory** is :file:`<app>/build`
17 makes it easier to use ``west build`` and other commands with it. (You can
19 <important-build-vars>` is set appropriately, though.)
24 Zephyr's build system is based on `CMake`_.
26 The build system is application-centric, and requires Zephyr-based applications
27 to initiate building the Zephyr source code. The application build controls
28 the configuration and build process of both the application and Zephyr itself,
32 and build system. You also likely have installed various :ref:`modules`
37 application. This directory contains all application-specific files, such as
[all …]
/Zephyr-latest/doc/develop/debug/
Dindex.rst11 This section is a quick hands-on reference to start debugging your
27 debugging purposes. The build system generates the image in the build
46 .. code-block:: bash
48 qemu -s -S <image>
54 * ``-S`` Do not start CPU at startup; rather, you must type 'c' in the
56 * ``-s`` Shorthand for :literal:`-gdb tcp::1234`: open a GDB server on
60 Running QEMU via :command:`ninja`
63 Run the following inside the build directory of an application:
65 .. code-block:: console
67 ninja debugserver
[all …]
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/
DREADME.txt7 ARM Cortex-M targets.
9 ---------------------------------------------------------------------------
16 ninja/make run
18 ---------------------------------------------------------------------------
22 Problems caused by out-dated project information can be addressed by
25 ninja/make clean # discard results of previous builds
28 ninja/make pristine # discard results of previous builds
29 # and restore pre-defined configuration info
31 ---------------------------------------------------------------------------
35 ***** Booting Zephyr OS build zephyr-v1.14.0-1726-gb95a71960622 *****
[all …]
/Zephyr-latest/tests/arch/arm/arm_tz_wrap_func/src/
DREADME.txt9 - The wrapper functions are correctly called.
10 - The arguments are passed to the wrapped function.
11 - The return value from the wrapped function is correctly returned from the
14 ---------------------------------------------------------------------------
21 ninja/make run
23 ---------------------------------------------------------------------------
27 Problems caused by out-dated project information can be addressed by
30 ninja/make clean # discard results of previous builds
33 ninja/make pristine # discard results of previous builds
34 # and restore pre-defined configuration info
[all …]
/Zephyr-latest/cmake/usage/
Dusage.cmake1 # SPDX-License-Identifier: Apache-2.0
7 if(${generator} STREQUAL ninja)
8 set(verbose "-v")
14 message(" clean - Remove most generated files but keep configuration and backup files")
15 message(" pristine - Remove all files in the build directory")
18 message(" menuconfig - Update .config using a console-based interface")
19 message(" guiconfig - Update .config using a graphical interface")
22 message(" all - Build a zephyr application")
23 message(" run - Build a zephyr application and run it if the board supports emulation")
24 message(" flash - Run \"west flash\"")
[all …]
/Zephyr-latest/samples/tfm_integration/psa_crypto/
DREADME.rst1 .. zephyr:code-sample:: tfm_psa_crypto
2 :name: TF-M PSA crypto
8 This TF-M integration example demonstrates how to use the PSA crypto API in
10 this example also demonstrates certain TF-M features that are covered as part
15 Trusted Firmware (TF-M) Platform Security Architecture (PSA) APIs
17 non-secure processing environment.
20 handle secure TF-M API calls and responses.
22 The sample prints test info to the console either as a single-thread or
23 multi-thread application.
26 https://www.psacertified.org/security-certification/psa-certified-level-1/
[all …]
/Zephyr-latest/tests/bsim/
Dcompile.source2 # SPDX-License-Identifier: Apache-2.0
8 WORK_DIR="${WORK_DIR:-${ZEPHYR_BASE}/bsim_out}"
11 echo -e "\033[0;31mFailure building ${app} ${conf_file} for ${BOARD}\033[0m\n\
13 "${cmake_cmd[@]@Q}" && ninja ${ninja_args}"
19 local app_root="${app_root:-${ZEPHYR_BASE}}"
20 local BOARD_ROOT="${BOARD_ROOT:-${ZEPHYR_BASE}}"
21 local conf_file="${conf_file:-prj.conf}"
22 local extra_conf_file="${extra_conf_file:-""}"
23 local conf_overlay="${conf_overlay:-""}"
24 local snippet="${snippet:-""}"
[all …]
/Zephyr-latest/doc/build/sysbuild/
Dindex.rst3 Sysbuild (System build)
6 Sysbuild is a higher-level build system that can be used to combine multiple
7 other build systems together. It is a higher-level layer that combines one
8 or more Zephyr build systems and optional additional build systems
9 into a hierarchical build system.
11 For example, you can use sysbuild to build a Zephyr application together
19 Like Zephyr's :ref:`build system <build_overview>`, sysbuild is written in
27 Single-image build
29 build system.
31 Multi-image build
[all …]
/Zephyr-latest/tests/arch/common/ramfunc/
DREADME.txt11 ---------------------------------------------------------------------------
18 ninja/make run
20 ---------------------------------------------------------------------------
24 Problems caused by out-dated project information can be addressed by
27 ninja/make clean # discard results of previous builds
30 ninja/make pristine # discard results of previous builds
31 # and restore pre-defined configuration info
33 ---------------------------------------------------------------------------
37 *** Booting Zephyr OS build zephyr-v3.4.0-4114-gadfd4017979f ***
40 START - test_ramfunc
[all …]
/Zephyr-latest/scripts/tests/twister/
Dtest_environment.py5 # SPDX-License-Identifier: Apache-2.0
25 ['--short-build-path', '-k'],
26 '--short-build-path requires Ninja to be enabled'
32 ['--device-serial-pty', 'dummy'],
33 '--device-serial-pty is not supported on Windows OS'
39 ['--west-runner=dummy'],
40 'west-runner requires west-flash to be enabled'
46 ['--west-flash=\"--board-id=dummy\"'],
47 'west-flash requires device-testing to be enabled'
56 ['--enable-valgrind'],
[all …]
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_linux.rst32 .. group-tab:: Ubuntu
34 .. code-block:: console
36 sudo apt-get update
37 sudo apt-get upgrade
39 .. group-tab:: Fedora
41 .. code-block:: console
45 .. group-tab:: Clear Linux
47 .. code-block:: console
51 .. group-tab:: Arch Linux
53 .. code-block:: console
[all …]
/Zephyr-latest/doc/build/cmake/
Dindex.rst1 .. _cmake-details:
3 Build System (CMake)
7 CMake is used to build your application together with the Zephyr kernel. A
8 CMake build is done in two stages. The first stage is called
9 **configuration**. During configuration, the CMakeLists.txt build scripts are
11 Zephyr build, and can generate build scripts that are native to the host
14 CMake supports generating scripts for several build systems, but only Ninja and
16 **build** stage by executing the generated build scripts. These build scripts
19 be executed again before building. The build scripts can detect some of these
23 Zephyr uses CMake's concept of a 'target' to organize the build. A
[all …]
/Zephyr-latest/scripts/net/
Drun-sample-tests.sh3 # SPDX-License-Identifier: Apache-2.0
5 image=net-tools
6 name=net-tools
7 network=net-tools0
14 docker_test_script_name=docker-test.sh
24 if [ -z "$ZEPHYR_BASE" ]; then
27 elif [ ! -d "$ZEPHYR_BASE" ]; then
32 if [ -z "$NET_TOOLS_BASE" ]; then
39 l="$d/tools/net-tools"
40 if [ -d "$l" ]; then
[all …]
/Zephyr-latest/tests/arch/arm/arm_irq_advanced_features/
DREADME.txt1 Title: Test to verify advanced features of ARM Cortex-M interrupt handling.
9 installed at run-time in the software interrupt table.
10 Only for ARMv7-M and ARMv8-M Mainline targets.
15 cannot be masked-out by irq_lock()).
16 Only for ARMv7-M and ARMv8-M Mainline targets.
19 TrustZone-M enabled Cortex-M Mainline CPUs.
21 ---------------------------------------------------------------------------
28 ninja/make run
30 ---------------------------------------------------------------------------
34 Problems caused by out-dated project information can be addressed by
[all …]
/Zephyr-latest/scripts/
Dlist_shields.py5 # SPDX-License-Identifier: Apache-2.0
12 # This is shared code between the build system's 'shields' target
17 # 'ninja shields' in a build directory without west installed.)
49 shield_name = file_name[:-len('.overlay')]
60 # Remember to update west-completion.bash if you add or remove
62 parser.add_argument("--board-root", dest='board_roots', default=[],
/Zephyr-latest/doc/build/kconfig/
Dmenuconfig.rst8 ``guiconfig``. ``menuconfig`` is a curses-based interface that runs in the
14 the application build directory by hand. Using one of the configuration
20 re-configuring.
33 #. Build your application as usual using either ``west`` or ``cmake``:
35 .. zephyr-app-commands::
37 :cd-into:
39 :goals: build
42 #. To run the terminal-based ``menuconfig`` interface, use either of these
45 .. code-block:: bash
47 west build -t menuconfig
[all …]
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.zsh4 # SPDX-License-Identifier: Apache-2.0
6 # Ensure this works also when being source-ed
9 typeset -A -g _opt_args
12 local -a builtin_cmds=(
25 local -a zephyr_ext_cmds=(
28 'build[compile a Zephyr application]'
29 'sign[sign a Zephyr binary for bootloader chain-loading]'
34 'zephyr-export[export Zephyr installation as a CMake config package]'
40 local -a all_cmds=(${builtin_cmds} ${zephyr_ext_cmds})
42 if [[ -v WEST_COMP_CHECK_WORKSPACE ]]; then
[all …]
/Zephyr-latest/.github/workflows/
Ddoc-build.yml2 # SPDX-License-Identifier: Apache-2.0
4 name: Documentation Build
8 - cron: '0 */3 * * *'
11 - v*
22 # and each sphinx-build process may use more than 2GiB of RAM.
26 doc-file-check:
28 runs-on: ubuntu-22.04
30 github.repository_owner == 'zephyrproject-rtos'
32 file_check: ${{ steps.check-doc-files.outputs.any_modified }}
34 - name: checkout
[all …]

123