| /third_party/ninja/ |
| D | README.md | 1 # Ninja chapter
3 Ninja is a small build system with a focus on speed.
4 https://ninja-build.org/
6 See [the manual](https://ninja-build.org/manual.html) or
11 [GitHub](https://github.com/ninja-build/ninja/releases).
12 Run `./ninja -h` for Ninja help.
15 resulting ninja binary. However, to enable features like Bash
19 If you're interested in making changes to Ninja, read
22 ## Building Ninja itself
24 You can either build Ninja via the custom generator script written in Python or
[all …]
|
| D | configure.py | 17 """Script that generates the build.ninja for ninja itself.
19 Projects that use ninja themselves should either write a similar script
20 or use a meta-build system that supports Ninja output."""
120 Used to bootstrap Ninja from scratch. In --bootstrap mode this
142 # In bootstrap mode, we have no ninja process to catch /showIncludes
157 # Implement just enough of Ninja variable expansion etc. to
200 help='bootstrap a ninja binary from nothing')
234 BUILD_FILENAME = 'build.ninja'
246 print('bootstrapping ninja...')
249 n.comment('This file is used to build ninja itself.')
[all …]
|
| D | CMakeLists.txt | 6 option(NINJA_BUILD_BINARY "Build ninja binary" ON)
9 project(ninja CXX) project
67 # the depfile parser and ninja lexers are generated using re2c.
121 # Core source files all build into ninja library.
159 # compiler may build ninja.
167 # compiler may build ninja.
192 add_executable(ninja src/ninja.cc) target
193 target_link_libraries(ninja PRIVATE libninja libninja-re2c)
196 target_sources(ninja PRIVATE windows/ninja.manifest)
200 # Adds browse mode into the ninja binary if it's supported by the host platform.
[all …]
|
| /third_party/node/doc/contributing/ |
| D | building-node-with-ninja.md | 1 # Building Node.js with Ninja
3 The purpose of this guide is to show how to build Node.js using [Ninja][], as
5 [Ninja's site][Ninja] for installation instructions (Unix only).
7 [Ninja][] is supported in the Makefile. Run `./configure --ninja` to configure
8 the project to run the regular `make` commands with Ninja.
10 For example, `make` will execute `ninja -C out/Release` internally
19 ninja: Entering directory `out/Release`
25 produce and is one of the benefits of using Ninja. When using Ninja, builds
31 make -j4 # With this flag, Ninja will limit itself to 4 parallel jobs,
40 ./configure --ninja --debug && make
[all …]
|
| /third_party/ninja/doc/ |
| D | manual.asciidoc | 1 The Ninja build system
9 Ninja is yet another build system. It takes as input the
13 Ninja joins a sea of other build systems. Its distinguishing goal is
15 http://neugierig.org/software/chromium/notes/2011/02/ninja.html[my
19 after changing one file. Ninja is under a second.
24 Where other build systems are high-level languages, Ninja aims to be
32 Ninja contains the barest functionality necessary to describe
36 Instead, Ninja is intended to be used with a separate program
42 build a debug or release-mode binary?" belong in the `.ninja` file
48 Here are the design goals of Ninja:
[all …]
|
| /third_party/ninja/misc/ |
| D | ninja-mode.el | 1 ;;; ninja-mode.el --- Major mode for editing .ninja files -*- lexical-binding: t -*-
21 ;; Simple emacs mode for editing .ninja files.
25 (defcustom ninja-indent-offset 2
29 :group 'ninja)
31 (defconst ninja-keywords-re
35 (defvar ninja-keywords
36 `((,ninja-keywords-re . font-lock-keyword-face)
48 (defvar ninja-mode-syntax-table
52 "Syntax table used in `ninja-mode'.")
54 (defun ninja-syntax-propertize (start end)
[all …]
|
| D | ninja.vim | 1 " ninja build file syntax.
2 " Language: ninja build file as described at
3 " http://ninja-build.org/manual.html
11 " ninja lexer and parser are at
12 " https://github.com/ninja-build/ninja/blob/master/src/lexer.in.cc
13 " https://github.com/ninja-build/ninja/blob/master/src/manifest_parser.cc
84 let b:current_syntax = "ninja"
|
| /third_party/ninja/.github/workflows/ |
| D | linux.yml | 30 - name: Build debug ninja
39 - name: Test debug ninja
43 - name: Build release ninja
48 strip release-build/ninja
50 - name: Test release ninja
54 - name: Create ninja archive
57 7z a artifact/ninja-linux.zip ./release-build/ninja
59 # Upload ninja binary archive as an artifact
63 name: ninja-binary-archives
73 asset_path: ./artifact/ninja-linux.zip
[all …]
|
| D | windows.yml | 28 - name: Build ninja
35 - name: Test ninja (Debug)
40 - name: Test ninja (Release)
45 - name: Create ninja archive
49 7z a artifact/ninja-win${{ matrix.suffix }}.zip ./build/Release/ninja.exe
51 # Upload ninja binary archive as an artifact
55 name: ninja-binary-archives
65 asset_path: ./artifact/ninja-win${{ matrix.suffix }}.zip
66 asset_name: ninja-win${{ matrix.suffix }}.zip
|
| D | macos.yml | 19 - name: Build ninja
27 - name: Test ninja
31 - name: Create ninja archive
35 7z a artifact/ninja-mac.zip ./build/Release/ninja
37 # Upload ninja binary archive as an artifact
41 name: ninja-binary-archives
51 asset_path: ./artifact/ninja-mac.zip
52 asset_name: ninja-mac.zip
|
| /third_party/gn/src/gn/ |
| D | ninja_tools.h | 13 // Invokes the ninja restat tool (ie, ninja -C build_dir -t restat). This tool
14 // tells ninja that it should check the mtime of the provided files and update
16 // in the ninja graph has been updated without invoking ninja.
18 // The best example of this is after gn gen runs, we know that build.ninja has
19 // been potentially updated, but ninja will still use the mtime from the
20 // .ninja_log and could trigger another re-gen. By telling ninja to restat
21 // build.ninja, we can eliminate the extra re-gen.
23 // If files_to_restat is empty, ninja will restat all files that have an entry
30 // Invokes the ninja cleandead tool (ie, ninja -C build_dir -t cleandead). This
37 // Invokes the ninja recompact tool (ie, ninja -C build_dir -t recompact). This
|
| D | ninja_build_writer.h | 27 // Generates the toplevel "build.ninja" file. This references the individual
51 // Extracts from an existing build.ninja file's contents the commands
52 // necessary to run GN and regenerate build.ninja.
54 // The regeneration rules live at the top of the build.ninja file and their
64 // WriteNinjaRules writes the rules that ninja uses to regenerate its own
67 // Ninja file regeneration is accomplished by two separate build statements.
68 // This is necessary to work around ninja's behavior of deleting all output
70 // it can complete. Previously, interrupting regeneration would cause ninja to
71 // delete build.ninja, losing any flags/build settings passed to gen
74 // The workaround involves misleading ninja about when the build.ninja file is
[all …]
|
| D | command_gen.cc | 57 const char kSwitchNinjaExecutable[] = "ninja-executable";
58 const char kSwitchNinjaExtraArgs[] = "ninja-extra-args";
59 const char kSwitchNinjaOutputsFile[] = "ninja-outputs-file";
60 const char kSwitchNinjaOutputsScript[] = "ninja-outputs-script";
61 const char kSwitchNinjaOutputsScriptArgs[] = "ninja-outputs-script-args";
82 // Collects Ninja rules for each toolchain. The lock protects the rules
98 // Called on worker thread to write the ninja file.
438 // tools. Since these tools can re-write ninja build log and dep logs, it is in RunNinjaPostProcessTools()
439 // really important that ninja executable used for tools matches the in RunNinjaPostProcessTools()
443 *err = Err(Location(), "No --ninja-executable provided.", in RunNinjaPostProcessTools()
[all …]
|
| D | ninja_build_writer.cc | 65 // Use "." for the directory to generate. When Ninja runs the command it in GetSelfInvocationCommandLine()
119 // the regeneration is invoked by ninja, the gen command is aware that it is a in GetSelfInvocationCommandLine()
121 // command to elide ninja post processing steps that ninja will perform in GetSelfInvocationCommandLine()
227 ScopedTrace trace(TraceItem::TRACE_FILE_WRITE_NINJA, "build.ninja"); in RunAndWriteFile()
265 // Unconditionally write the build.ninja. Ninja's build-out-of-date in RunAndWriteFile()
266 // checking will re-run GN when any build input is newer than build.ninja, so in RunAndWriteFile()
267 // any time the build is updated, build.ninja's timestamp needs to updated in RunAndWriteFile()
270 SourceFile(build_settings->build_dir().value() + "build.ninja"))); in RunAndWriteFile()
280 SourceFile(build_settings->build_dir().value() + "build.ninja.d"))); in RunAndWriteFile()
287 // Finally, write the empty build.ninja.stamp file. This is the output in RunAndWriteFile()
[all …]
|
| D | command_clean_stale.cc | 33 // 2. recompact - This prunes old entries from the ninja log and deps files. in CleanStaleOneDir()
36 // be found during the recompact, so ninja can prune their entries. in CleanStaleOneDir()
56 R"(gn clean_stale [--ninja-executable=...] <out_dir>...
59 their records from the ninja build log and dependency database. These are
63 This command requires a ninja executable of at least version 1.10.0. The
64 executable must be provided by the --ninja-executable switch.
68 --ninja-executable=<string>
69 Can be used to specify the ninja executable to use.
84 Err(Location(), "No --ninja-executable provided.", in RunCleanStale()
85 "--clean-stale requires a ninja executable to run. You can " in RunCleanStale()
[all …]
|
| /third_party/opencl-headers/.github/workflows/ |
| D | windows.yml | 18 GEN: Ninja Multi-Config
22 NINJA_URL: https://github.com/ninja-build/ninja/releases/download/v1.10.2/ninja-win.zip
23 NINJA_ROOT: C:\Tools\Ninja
30 - name: Cache Ninja install
31 if: matrix.GEN == 'Ninja Multi-Config'
32 id: ninja-install
36 C:\Tools\Ninja
37 key: ${{runner.os}}-ninja-${{env.NINJA_URL}}
39 - name: Install Ninja
40 if: matrix.GEN == 'Ninja Multi-Config' && steps.ninja-install.outputs.cache-hit != 'true'
[all …]
|
| /third_party/skia/third_party/externals/angle2/infra/specs/ |
| D | angle.json | 40 "test_id_prefix": "ninja://src/tests:angle_deqp_egl_tests/",
77 "test_id_prefix": "ninja://src/tests:angle_deqp_egl_tests/",
114 "test_id_prefix": "ninja://src/tests:angle_deqp_gles2_tests/",
151 "test_id_prefix": "ninja://src/tests:angle_deqp_gles2_tests/",
188 "test_id_prefix": "ninja://src/tests:angle_deqp_gles31_tests/",
225 "test_id_prefix": "ninja://src/tests:angle_deqp_gles3_tests/",
262 "test_id_prefix": "ninja://src/tests:angle_deqp_gles3_tests/",
298 "test_id_prefix": "ninja://src/tests:angle_deqp_khr_gles2_tests/",
335 "test_id_prefix": "ninja://src/tests:angle_deqp_khr_gles31_tests/",
371 "test_id_prefix": "ninja://src/tests:angle_deqp_khr_gles32_tests/",
[all …]
|
| /third_party/ninja/misc/packaging/ |
| D | ninja.spec | 1 Summary: Ninja is a small build system with a focus on speed.
2 Name: ninja
7 URL: https://github.com/ninja-build/ninja
14 Ninja is yet another build system. It takes as input the interdependencies of files (typically sour…
17 Ninja joins a sea of other build systems. Its distinguishing goal is to be fast. It is born from my…
19 seconds to start building after changing one file. Ninja is under a second.
27 ./ninja manual
31 cp -p ninja %{buildroot}%{_bindir}/
|
| D | rpmbuild.sh | 3 echo Building ninja RPMs..
14 git archive --format=tar --prefix=ninja-${VER}-${REL}/ HEAD | gzip -c > $RPMTOPDIR/SOURCES/ninja-${…
17 sed -e "s/%{ver}/$VER/" -e "s/%{rel}/$REL/" misc/packaging/ninja.spec > $RPMTOPDIR/SPECS/ninja.spec
18 …aN%n- (%h) %s%d%n" --date=local | sed -r 's/[0-9]+:[0-9]+:[0-9]+ //' >> $RPMTOPDIR/SPECS/ninja.spec
26 -ba $RPMTOPDIR/SPECS/ninja.spec &&
|
| /third_party/node/deps/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/ |
| D | ninja_test.py | 7 """ Unit tests for the ninja.py file. """
12 import gyp.generator.ninja as ninja namespace
20 writer = ninja.NinjaWriter(
21 "foo", "wee", ".", ".", "build.ninja", ".", "build.ninja", "win"
35 writer = ninja.NinjaWriter(
36 "foo", "wee", ".", ".", "build.ninja", ".", "build.ninja", "linux"
|
| /third_party/node/tools/gyp/pylib/gyp/generator/ |
| D | ninja_test.py | 7 """ Unit tests for the ninja.py file. """
12 import gyp.generator.ninja as ninja namespace
20 writer = ninja.NinjaWriter(
21 "foo", "wee", ".", ".", "build.ninja", ".", "build.ninja", "win"
35 writer = ninja.NinjaWriter(
36 "foo", "wee", ".", ".", "build.ninja", ".", "build.ninja", "linux"
|
| /third_party/spirv-tools/kokoro/scripts/macos/ |
| D | build.sh | 32 # Get NINJA.
33 wget -q https://github.com/ninja-build/ninja/releases/download/v1.8.2/ninja-mac.zip
34 unzip -q ninja-mac.zip
35 chmod +x ninja
56 ninja
64 ninja install
|
| /third_party/skia/third_party/externals/tint/ |
| D | CMakeSettings.json | 5 "generator": "Ninja",
17 "generator": "Ninja",
29 "generator": "Ninja",
41 "generator": "Ninja",
53 "generator": "Ninja",
65 "generator": "Ninja",
77 "generator": "Ninja",
89 "generator": "Ninja",
|
| /third_party/node/deps/npm/node_modules/node-gyp/gyp/pylib/gyp/ |
| D | xcode_ninja.py | 5 """Xcode-ninja wrapper project file generator.
8 with ninja instead. The Xcode project itself is transformed into a list of
9 executable targets, each with a build step to build with ninja, and a target
16 import gyp.generator.ninja
59 """ Create fake target for xcode-ninja wrapper. """
60 # Determine ninja top level build dir (e.g. /path/to/out).
66 options.toplevel_dir, gyp.generator.ninja.ComputeOutputDir(params)
118 "action_name": "Compile and copy %s via ninja" % target_name,
124 "ninja",
129 "message": "Compile and copy %s via ninja" % target_name,
[all …]
|
| /third_party/node/tools/gyp/pylib/gyp/ |
| D | xcode_ninja.py | 5 """Xcode-ninja wrapper project file generator.
8 with ninja instead. The Xcode project itself is transformed into a list of
9 executable targets, each with a build step to build with ninja, and a target
16 import gyp.generator.ninja
59 """ Create fake target for xcode-ninja wrapper. """
60 # Determine ninja top level build dir (e.g. /path/to/out).
66 options.toplevel_dir, gyp.generator.ninja.ComputeOutputDir(params)
118 "action_name": "Compile and copy %s via ninja" % target_name,
124 "ninja",
129 "message": "Compile and copy %s via ninja" % target_name,
[all …]
|