Home
last modified time | relevance | path

Searched refs:build (Results 1 – 25 of 1426) sorted by relevance

12345678910>>...58

/Zephyr-latest/doc/develop/west/
Dbuild-flash-debug.rst1 .. _west-build-flash-debug:
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
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
33 - If there is a Zephyr build directory named :file:`build` in your current
35 run ``west build`` from a Zephyr build directory.
37 - Otherwise, if you run ``west build`` from a Zephyr application's source
38 directory and no build directory is found, a new one is created and the
44 The easiest way to use ``west build`` is to go to an application's root
[all …]
Dwithout-west.rst13 - specifying the locations of these repositories to the Zephyr build
27 Otherwise, Zephyr's build system will find it and may try to use
52 You can build a Zephyr application using CMake and Ninja (or make) directly
58 :goals: build
62 When building with west installed, the Zephyr build system will use it to set
63 :ref:`ZEPHYR_MODULES <important-build-vars>`.
66 these repositories, the build will still work.
81 Running build system targets like ``ninja flash``, ``ninja debug``,
83 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
89 If you want to use these build system targets but do not want to
[all …]
/Zephyr-latest/doc/build/cmake/
Dindex.rst7 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
26 understand. All source code that goes into a Zephyr build does so by
30 build scripts like this:
[all …]
/Zephyr-latest/tests/subsys/jwt/src/
Dmain.c36 struct jwt_builder build; in ZTEST() local
39 res = jwt_init_builder(&build, buf, sizeof(buf)); in ZTEST()
43 res = jwt_add_payload(&build, 1530312026, 1530308426, in ZTEST()
47 res = jwt_sign(&build, jwt_test_private_der, jwt_test_private_der_len); in ZTEST()
50 zassert_equal(build.overflowed, false, "Not overflow"); in ZTEST()
/Zephyr-latest/scripts/pylib/pytest-twister-harness/
DREADME.rst29 or build shell application by west and call pytest directly:
38 west build -p -b native_sim -- -DCONFIG_NATIVE_UART_0_ON_STDINOUT=y
39 pytest --twister-harness --device-type=native --build-dir=build -p twister_harness.plugin
42 west build -p -b qemu_x86 -- -DQEMU_PIPE=qemu-fifo
43 pytest --twister-harness --device-type=qemu --build-dir=build -p twister_harness.plugin
46 west build -p -b nrf52840dk/nrf52840
47 …pytest --twister-harness --device-type=hardware --device-serial=/dev/ttyACM0 --build-dir=build -p …
Dpyproject.toml1 [build-system]
2 build-backend = "setuptools.build_meta"
/Zephyr-latest/subsys/bindesc/
DKconfig.build_time7 Add the build time binary descriptors
14 If enabled, the build time used for the descriptors will express
21 If enabled, the file containing the build time definitions will
23 accurate, but also in slightly longer build times.
26 bool "Year of build"
31 bool "Month of build"
36 bool "Day of build"
41 bool "Hour of build"
46 bool "Minute of build"
51 bool "Second of build"
[all …]
/Zephyr-latest/doc/build/snippets/
Dusing.rst11 Snippets have names. You use snippets by giving their names to the build
14 With west build
21 west build -S foo app
27 west build -S snippet1 -S snippet2 [...] app
32 If you are running CMake directly instead of using ``west build``, use the
39 cmake --build build
/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/boards/lilygo/ttgo_t7v1_5/doc/
Dindex.rst83 must be build (and flash) at least once.
88 2. Manual build
102 The sysbuild makes possible to build and flash all necessary images needed to
105 To build the sample application using sysbuild use the command:
111 :goals: build
119 Zephyr build. Output is structured by the domain subdirectories:
123 build/
136 With ``--sysbuild`` option the bootloader will be re-build and re-flash
137 every time the pristine build is used.
139 For more information about the system build please read the :ref:`sysbuild` documentation.
[all …]
/Zephyr-latest/doc/services/llext/
Dbuild.rst9 The easiest path to achieve this is to build the extension as part of the
11 <llext_build_native_>`_. This will result in a single build providing both the
15 In some cases, involving the full Zephyr build system may not be feasible or
27 The Zephyr build system provides a set of features that can be used to build
28 extensions as part of the Zephyr application. This is the simplest way to build
29 extensions, as it requires minimal additions to an application build system.
78 Tweaking the build process
81 The following CMake functions can be used to modify the build system behavior
82 during the extension build process to a fine degree. Each of the below
92 Custom build steps
[all …]
/Zephyr-latest/samples/application_development/external_lib/
DREADME.rst4 Include an external static library into the Zephyr build system.
10 into the Zephyr build system.
11 The demonstrates both how to build the external library using a different build
29 Once installed, build the application as normal.
37 getting the ``Complete package`` setup. Once installed and in the path, build
DCMakeLists.txt10 # how to build for this platform so we export all the flags used in
11 # this zephyr build to the external build system.
13 # Other external build systems may be self-contained enough that they
14 # do not need any build information from zephyr. Or they may be
32 # Add an external project to be able download and build the third
52 BINARY_DIR ${mylib_src_dir} # This particular build system is invoked from the root
60 INSTALL_COMMAND "" # This particular build system has no install command
/Zephyr-latest/modules/trusted-firmware-m/
DKconfig.tfm.partitions16 to be passed to the TF-M build system. Look at 'config_default.cmake'
19 options are handled by the build system in the trusted-firmware-m
27 to be passed to the TF-M build system. Look at 'config_default.cmake'
30 options are handled by the build system in the trusted-firmware-m
38 to be passed to the TF-M build system. Look at 'config_default.cmake'
41 options are handled by the build system in the trusted-firmware-m
50 to be passed to the TF-M build system. Look at 'config_default.cmake'
53 options are handled by the build system in the trusted-firmware-m
61 to be passed to the TF-M build system. Look at 'config_default.cmake'
64 options are handled by the build system in the trusted-firmware-m
[all …]
/Zephyr-latest/boards/franzininho/esp32s2_franzininho/doc/
Dindex.rst69 2. Manual build
83 The sysbuild makes possible to build and flash all necessary images needed to
86 To build the sample application using sysbuild use the command:
92 :goals: build
100 Zephyr build. Output is structured by the domain subdirectories:
104 build/
117 With ``--sysbuild`` option the bootloader will be re-build and re-flash
118 every time the pristine build is used.
120 For more information about the system build please read the :ref:`sysbuild` documentation.
122 Manual build
[all …]
/Zephyr-latest/cmake/
Dpristine.cmake7 usage: cmake -DBINARY_DIR=<build-path> -DSOURCE_DIR=<source-path>
11 -DBINARY_DIR=<build-path>: Absolute path to the build directory to pristine
13 creating <build-path>
32 message(FATAL_ERROR "Refusing to run pristine in in-source build folder.")
/Zephyr-latest/samples/kernel/bootargs/
DREADME.rst30 :goals: build run
37 *** Booting Zephyr OS build v3.7.0-514-gd4490bc739d1 ***
51 :goals: build run
58 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
59 argv[0] = /home/user/zephyr/samples/kernel/bootargs/build/zephyr/zephyr.elf
65 …qemu-system-x86_64 -kernel ./build/zephyr/zephyr.elf -nographic -append "This is 'a list of' argum…
71 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
72 argv[0] = ./build/zephyr/zephyr.elf
85 :goals: build run
100 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
[all …]
/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
38 during build time, which is not really practical. This sample is about the EDK
39 providing the ability to build extensions independently from the application.
40 One could build the extensions in different directories, not related to the
48 To build the EDK, use the ``llext-edk`` target. For example:
53 :goals: build llext-edk
62 cp build/zephyr/llext-edk.tar.xz /tmp/edk
84 To build the extensions, in the ``ext1``, ``ext2``, ``ext3`` and ``kext1``
89 cmake -B build
[all …]
/Zephyr-latest/samples/bluetooth/bap_unicast_client/
DREADME.rst37 :goals: build
43 You can build both the application core image and an appropriate controller image for the network
49 :goals: build
52 If you prefer to only build the application core image, you can do so by doing instead:
57 :goals: build
71 :goals: build
74 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
83 :goals: build
/Zephyr-latest/samples/bluetooth/bap_unicast_server/
DREADME.rst37 :goals: build
43 You can build both the application core image and an appropriate controller image for the network
49 :goals: build
52 If you prefer to only build the application core image, you can do so by doing instead:
57 :goals: build
71 :goals: build
74 Note this will produce a Linux executable in :file:`./build/zephyr/zephyr.exe`.
83 :goals: build
/Zephyr-latest/boards/lilygo/ttgo_t8c3/doc/
Dindex.rst96 2. Manual build
110 The sysbuild makes possible to build and flash all necessary images needed to
113 To build the sample application using sysbuild use the command:
119 :goals: build
127 Zephyr build. Output is structured by the domain subdirectories:
131 build/
144 With ``--sysbuild`` option the bootloader will be re-build and re-flash
145 every time the pristine build is used.
147 For more information about the system build please read the :ref:`sysbuild` documentation.
149 Manual build
[all …]
/Zephyr-latest/samples/posix/gettimeofday/
DMakefile.host4 mkdir -p build
5 $(CC) $^ -o build/$@
/Zephyr-latest/samples/posix/uname/
DMakefile.host4 mkdir -p build
5 $(CC) $^ -o build/$@
/Zephyr-latest/samples/posix/eventfd/
DMakefile.host4 mkdir -p build
5 $(CC) $^ -o build/$@
/Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/support/
Dappli_debug_cmd.gdb5 # works if the .elf is located in "build" directory
11 restore ./build/zephyr/zephyr.elf
12 symbol-file -readnow ./build/zephyr/zephyr.elf

12345678910>>...58