Name Description Size
aix
android
apple
BUILD.gn 654
cc_wrapper.gni 1536
clang_code_coverage_wrapper.py Removes code coverage flags from invocations of the Clang C/C++ compiler. If the GN arg `use_clang_coverage=true`, this script will be invoked by default. GN will add coverage instrumentation flags to almost all source files. This script is used to remove instrumentation flags from a subset of the source files. By default, it will not remove flags from any files. If the option --files-to-instrument is passed, this script will remove flags from all files except the ones listed in --files-to-instrument. This script also contains hard-coded exclusion lists of files to never instrument, indexed by target operating system. Files in these lists have their flags removed in both modes. The OS can be selected with --target-os. This script also contains hard-coded force lists of files to always instrument, indexed by target operating system. Files in these lists never have their flags removed in either mode. The OS can be selected with --target-os. The order of precedence is: force list, exclusion list, --files-to-instrument. The path to the coverage instrumentation input file should be relative to the root build directory, and the file consists of multiple lines where each line represents a path to a source file, and the specified paths must be relative to the root build directory. e.g. ../../base/task/post_task.cc for build directory 'out/Release'. The paths should be written using OS-native path separators for the current platform. One caveat with this compiler wrapper is that it may introduce unexpected behaviors in incremental builds when the file path to the coverage instrumentation input file changes between consecutive runs, so callers of this script are strongly advised to always use the same path such as "${root_build_dir}/coverage_instrumentation_input.txt". It's worth noting on try job builders, if the contents of the instrumentation file changes so that a file doesn't need to be instrumented any longer, it will be recompiled automatically because if try job B runs after try job A, the files that were instrumented in A will be updated (i.e., reverted to the checked in version) in B, and so they'll be considered out of date by ninja and recompiled. Example usage: clang_code_coverage_wrapper.py \\ --files-to-instrument=coverage_instrumentation_input.txt 11179
concurrent_links.gni 4297
cros
cros_toolchain.gni 3680
fuchsia
gcc_link_wrapper.py Runs a linking command and optionally a strip command. This script exists to avoid using complex shell commands in gcc_toolchain.gni's tool("link"), in case the host running the compiler does not have a POSIX-like shell (e.g. Windows). 3466
gcc_solink_wrapper.py Runs 'ld -shared' and generates a .TOC file that's untouched when unchanged. This script exists to avoid using complex shell commands in gcc_toolchain.gni's tool("solink"), in case the host running the compiler does not have a POSIX-like shell (e.g. Windows). 6791
gcc_toolchain.gni 29615
get_concurrent_links.py 4459
get_cpu_count.py 474
get_goma_dir.py 1359
goma.gni 1079
ios
kythe.gni 388
linux
mac
nacl
nacl_toolchain.gni 2439
OWNERS 105
rbe.gni 1514
toolchain.gni 4082
win
wrapper_utils.py Helper functions for gcc_toolchain.gni wrappers. 2875