Searched full:ninja (Results 1 – 25 of 72) sorted by relevance
123
| /Zephyr-latest/doc/develop/west/ |
| D | without-west.rst | 52 You can build a Zephyr application using CMake and Ninja (or make) directly
81 Running build system targets like ``ninja flash``, ``ninja debug``,
83 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
108 After that, and in order for ``ninja`` to be able to invoke ``west``
118 Note that ``west build`` invokes ``ninja``, among other
120 ``ninja`` involved by default, however, as ``west build`` does not
121 invoke ``ninja flash``, ``debug``, etc. The one exception is if you
125 flash``. Even in this case, ``ninja`` is only run once, as ``ninja
|
| /Zephyr-latest/cmake/toolchain/armclang/ |
| D | generic.cmake | 7 AND NOT ${CMAKE_GENERATOR} STREQUAL Ninja
11 "${CMAKE_VERSION}. Use the 'Ninja' generator or update to CMake >= 3.21."
|
| /Zephyr-latest/tests/bsim/ |
| D | compile.source | 13 "${cmake_cmd[@]@Q}" && ninja ${ninja_args}"
83 ninja ${ninja_args} &> ninja.out || \
84 { ret="$?"; print_error_info ; cat ninja.out && return $ret; }
|
| /Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/ |
| D | README.txt | 16 ninja/make run
25 ninja/make clean # discard results of previous builds
28 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/tests/arch/arm/arm_no_multithreading/ |
| D | README.txt | 23 ninja/make run
32 ninja/make clean # discard results of previous builds
35 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/tests/arch/arm/arm_tz_wrap_func/src/ |
| D | README.txt | 21 ninja/make run
30 ninja/make clean # discard results of previous builds
33 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | generation.rst | 195 # Use cmake to configure a Ninja-based build system:
201 # To generate HTML output, run ninja on the generated build system:
202 ninja html
203 # If you modify or add .rst files, run ninja again:
204 ninja html
206 # To generate PDF output, run ninja on the generated build system:
207 ninja pdf
226 of the build folder and run ``cmake`` and then ``ninja`` again.
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_environment.py | 26 '--short-build-path requires Ninja to be enabled'
137 'short build path without ninja',
263 ninja=True,
272 generator_cmd='ninja',
273 generator='Ninja',
284 ninja=False,
310 'ninja',
339 ninja=True
443 ninja=True
571 ninja=True
|
| /Zephyr-latest/tests/arch/common/ramfunc/ |
| D | README.txt | 18 ninja/make run
27 ninja/make clean # discard results of previous builds
30 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/samples/tfm_integration/tfm_ipc/ |
| D | README.rst | 98 ninja or make, adding the ``run`` commands:
108 $ ninja run
180 Example, for nRF9160, using ``cmake`` and ``ninja``
200 Example, for nRF9160, using ``cmake`` and ``ninja``
204 ninja flash
212 Example using ``cmake`` and ``ninja``
|
| /Zephyr-latest/tests/arch/arm/arm_irq_advanced_features/ |
| D | README.txt | 28 ninja/make run
37 ninja/make clean # discard results of previous builds
40 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/boards/electronut/nrf52840_blip/doc/ |
| D | index.rst | 121 ``ninja debug``, or ``ninja attach`` (or with ``make``) are available.
123 NOTE: You may need to press the reset button once after using ``ninja flash``
|
| /Zephyr-latest/boards/electronut/nrf52840_papyr/doc/ |
| D | nrf52840_papyr.rst | 133 ``ninja debug``, or ``ninja attach`` (or with ``make``) are available.
135 NOTE: You may need to press the reset button once after using ``ninja flash``
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap/ |
| D | README.txt | 52 ninja/make run
61 ninja/make clean # discard results of previous builds
64 ninja/make pristine # discard results of previous builds
|
| /Zephyr-latest/scripts/logging/dictionary/ |
| D | log_parser.py | 78 # When running QEMU via west or ninja, there may be additional
79 # strings printed by QEMU, west or ninja (for example, QEMU
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | application.py | 50 GENERATORS = ['make', 'ninja']
64 generator = self.options.get('generator', 'ninja').lower()
203 # west always defaults to ninja
353 # Prepare cmake/ninja/make variables
362 # Now generate the actual cmake and make/ninja commands
363 gen_arg = ' -GNinja' if generator == 'ninja' else ''
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 60 Running QEMU via :command:`ninja`
67 ninja debugserver
221 #. Configure your application with CMake and build it with ninja. Note the
222 different CMake generator specified by the ``-G"Eclipse CDT4 - Ninja"``
224 :file:`.project`, in addition to the usual ninja build files.
231 :gen-args: -G"Eclipse CDT4 - Ninja"
|
| /Zephyr-latest/scripts/tests/twister_blackbox/ |
| D | test_tooling.py | 98 'ninja',
103 ['--ninja', '-N']
|
| /Zephyr-latest/cmake/linker/lld/ |
| D | target.cmake | 25 elseif(CMAKE_GENERATOR STREQUAL "Ninja")
26 # Using DEPFILE with other generators than Ninja is an error.
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | app_smem.ld | 29 * Note: Ninja generator does not suffer from this issue.
|
| D | app_smem_pinned.ld | 33 * Note: Ninja generator does not suffer from this issue.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 81 ninja) ``ninja sysbuild_menuconfig`` to configure sysbuild or (if using make)
131 Here is an example using CMake and Ninja.
149 control the build process when using sysbuild with CMake and ninja.
151 To set number of jobs for ninja for all sysbuild images, set the CMAKE_BUILD_PARALLEL_LEVEL
433 ``mcuboot_``, using ninja or make - for details on how to run image build
448 image can be provided to west/ninja/make along with the name of the build
471 .. group-tab:: ``ninja``
474 using ``ninja`` using sysbuild with mcuboot enabled, the ``rom_report``
479 ninja -C mcuboot rom_report
486 ninja -C <app_name> -t tfm_rom_report
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 785 meta-tool, which invokes ``cmake`` and the underlying build tool (``ninja`` or
788 ``ninja``
789 generators (i.e. build tools), whereas on Windows you need to use ``ninja``,
791 For simplicity we will use ``ninja`` throughout this guide, and if you
793 default to ``ninja`` under the hood.
803 On Linux and macOS, you can also build with ``make`` instead of ``ninja``:
862 When using the Ninja generator a build directory looks like this:
867 ├── build.ninja
871 ├── rules.ninja
876 * :file:`build.ninja`, which can be invoked to build the application.
[all …]
|
| /Zephyr-latest/samples/tfm_integration/psa_crypto/ |
| D | README.rst | 98 Using ``cmake`` and ``ninja``
106 ninja
152 Using ``cmake`` and ``ninja``
160 ninja run
205 Example, for nRF9160, using ``cmake`` and ``ninja``
225 Example, for nRF9160, using ``cmake`` and ``ninja``
229 ninja flash
237 Example using ``cmake`` and ``ninja``
|
| /Zephyr-latest/cmake/linker/arcmwdt/ |
| D | target.cmake | 21 elseif(CMAKE_GENERATOR STREQUAL "Ninja")
22 # Using DEPFILE with other generators than Ninja is an error.
|
123
