参数改用别的生成器，例如 cmake -GNinja 会生成 Ninja 这个构建系统的构建规则。Ninja 是一个高性能，跨平台的构建系统，Linux、Windows、MacOS 上都可以用。 - Ninja 可以从包管理器里安装，没有包管理器的 Windows 可以用 Python 的包管理器安装： • pip install ninja（有趣的事实：CMake 也可以通过 pip install 虽然多核心但因历史兼容原因效率一般。 - 而 Ninja 则是专为性能优化的 cmake -GNinja -B build 合都是行业标准了。 bate@archer ~/Codes/course/11/template (master) $ ls build build.ninja CMakeCache.txt CMakeFiles cmake_install.cmake Ninja 和 Makefile 简单的对 简单的对 性能上：Ninja > Makefile > MSBuild Makefile 启动时会把每个文件都检测一遍，浪费很多时间。特别是有很多文件，但是实际需要构建的只有一小部分，从而是 I/O Bound 的时候，Ninja 的速度提升就很明显。 然而某些专利公司的 CUDA toolkit 在 Windows 上只允许用 MSBuild 构建，不能用 Ninja（怕不是和 Bill

/7a147c91233c81eec8ef7339e0086fce/p5_1.jpg) ## What is this talk? Visualizing Compilation with Ninja and Clang  Speed 8ef7339e0086fce/p17_1.jpg) ### .ninja_log - Tracks start/stop time in ms - Name of the output file - Hash of the command used (compiler, linker, etc) |1 # ninja|log v5||||| |---|---|---|---|---|---| tbody> ## ninjatracing - Convert .ninja_log files to chrome tracing format - Embed -ftime-trace .json files ninjatracing Public Convert .ninja_log files to chrome's about:tracing format

• Added support to ninja in 2015 for Fortran dep file depends - funded by the Trilinos project forked ninja - dyndep https://ninja-build.org/manual.html#ref_dyndep - May 2019 ninja merged all of the changes changes to support Fortran because of C++ modules! #### https://ninja-build.org/manual.html#ref_dyndep Some use cases require implicit dependency information to be dynamically • A Fortran parser based off of makedepf90 — CAN NOT/WILL NOT DO THIS FOR C++ • Patches made to ninja build tool now upstream - The dynamic dependency collator inside CMake ## kitware # Feb 2019 #

support was added to the ninja build tool to support Fortran modules. In 2019 with news of modules being added to C++, the Kitware fork of ninja was rejoined with upstream ninja and dynamic dependencies dependencies were added to ninja. This blog describes the process that was taken and the current state of named C++ 20 modules in CMake. Header modules are not covered in this blog. ## CMake: • Version 3.25 - - Version 3.28 for gcc14 support (to be released) ## Build tools: • Ninja 1.10 • MSBuild ## Dependency scanning - not the only approach - Build2 module support (2 years ago) predates dependency scanning

resource-intensive targets can reduce the level of parallelism on-demand ## Parallelism Level 4 - Ninja You can define separate job-pools each of which with a different size (eg: link=1 and cc=16) ## Will inputs and configuration, a target should yield identical outputs Reproducibility Level 1 - Make, Ninja, FASTBuild Provide no real facility to ensure reproducibility and, thus, hermeticity is something prefix • Just build in the same environment • At the same path • But how? Let's merge Git and Ninja! Because we can use Git : • Content Addressable Filesystem • to clone sources and build trees in

Usage - Generated by the build system (CMake, Meson, etc.) - Can also be generated by ninja itself with ninja -t compdb - Other tools like bear can extract a database from a build via tracing - - Generally available at the same time as the build instructions (Makefile, build.ninja, etc.) - Use it as soon as you have a configured build tree - Some exceptions apply ## Compilation Databases: order compilations • Vendored into CMake for its Unix Makefiles generator • dyndep support added to ninja, merged into 1.10 (released Jan 2020) ## C++ Modules: Example Target add_library(A) target_sources(A)

 GNU Make 忍者 Ninja  MSBuild Ships with [Image](/uploads/documents/d/8/c/a/d8cab3cbc32f88e7676019e359520730/p43_2.jpg) GNU Make # 忍者 Ninja Build & Project Systems  GNU Make 忍者 Ninja Build & Project Systems # 忍者 ## Ninja 忍者 Ninja Runs on many platforms Open source https://ninja-build.org Language agnostic Focused on minimal

practice tool_requires and tool packages are intended for executable applications, like cmake or ninja. Do not use tool_requires to depend on library or library-like dependencies. ## See also: • Using practice tool_requires and tool packages are intended for executable applications, like cmake or ninja that can be used as tool_requires("cmake/[>=3.25]") by other packages to put those executables ## Using CMakeToolchain with different generators: Ninja example This guide demonstrates how to use CMakeToolchain with predefined generators like Ninja and how to configure it to use different generators

practice tool_requires and tool packages are intended for executable applications, like cmake or ninja. Do not use tool_requires to depend on library or library-like dependencies. ## See also: • Using practice tool_requires and tool packages are intended for executable applications, like cmake or ninja that can be used as tool_requires("cmake/[>=3.25]") by other packages to put those executables ## Using CMakeToolchain with different generators: Ninja example This guide demonstrates how to use CMakeToolchain with predefined generators like Ninja and how to configure it to use different generators

practice tool_requires and tool packages are intended for executable applications, like cmake or ninja. Do not use tool_requires to depend on library or library-like dependencies. ## See also: • Using practice tool_requires and tool packages are intended for executable applications, like cmake or ninja that can be used as tool_requires("cmake/[>=3.25]") by other packages to put those executables ## Using CMakeToolchain with different generators: Ninja example This guide demonstrates how to use CMakeToolchain with predefined generators like Ninja and how to configure it to use different generators