Lines Matching +full:storage +full:- +full:repo +full:- +full:branch +full:- +full:coverage

14 [depot_tools](https://www.chromium.org/developers/how-tos/depottools) repo.
23 Note that openscreen does not use other features of `depot_tools` like `repo` or
24 `drover`.  However, some `git-cl` functions *do* work, like `git cl try`,
42 code, all third-party dependencies, and the toolchain needed to build things;
55 This will rebase any local commits on the remote top-of-tree, and update any
62  - Build file generator: `gn`
63  - Code formatter: `clang-format`
64  - Builder: `ninja` ([GitHub releases](https://github.com/ninja-build/ninja/releases))
65  - Compiler/Linker: `clang` (installed by default) or `gcc` (installed by you)
67 All of these--except `gcc` as noted above--are automatically downloaded/updated
73 `clang-format` is used for maintaining consistent coding style, but it is not a
75 The presubmit script will sanity-check that it has been run on all new/changed
81 Google storage cache, the same way that Chromium does it.
87    sudo apt-get install libstdc++-8-dev
96   mkdir out/debug-gcc
97   gn gen out/debug-gcc --args="is_gcc=true"
104   sudo apt-get install gcc-7
118   gn gen out/debug --args="is_debug=true"
124    sudo apt-get install libstdc++6-8-dbg
149   ninja -C out/debug osp_demo  # Builds the executable with ninja
153 The `-C` argument to `ninja` works just like it does for GNU Make: it specifies
164 edited a `BUILD.gn` file, `ninja` will re-run `gn` for you.
167 `autoninja` instead of `ninja`, which takes the same command-line arguments.
175 Running `ninja -C out/debug gn_all` will build all non-test targets in the
178 `gn ls --type=executable out/debug` will list all of the executable targets
182 pull up an editor for build flags. `gn args --list out/debug` prints all of
188   ninja -C out/debug openscreen_unittests
197 This library uses [Chromium Gerrit](https://chromium-review.googlesource.com/) for
199 for an account at `chromium-review.googlesource.com` to upload patches for review.
216 The first command will will auto-format the code changes. Then, the second
218 newcode review will be posted on `chromium-review.googlesource.com`.
220 If you make additional commits to your local branch, then running `git cl
221 upload` again in the same branch will merge those commits into the ongoing
224 It's simplest to create a local git branch for each patch you want reviewed
226 branch.
232 instructions above to rebase your commits on top-of-tree and upload a new
240 review to avoid extra back-and-forth.
263 * [Unit test code coverage](docs/code_coverage.md)