Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(131)

Unified Diff: tools/gn/command_args.cc

Issue 895433002: gn: Use the term 'out_dir' consistently when referring to the output directory. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | tools/gn/command_gen.cc » ('j') | tools/gn/command_refs.cc » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/gn/command_args.cc
diff --git a/tools/gn/command_args.cc b/tools/gn/command_args.cc
index 50bdbe913faae97b84811407209857710954cc1a..aca026d2f8e2fbdf9ab39269185a92c01a1ce803 100644
--- a/tools/gn/command_args.cc
+++ b/tools/gn/command_args.cc
@@ -245,7 +245,7 @@ int EditArgsFile(const std::string& build_dir) {
"# Build arguments go here. Examples:\n"
"# is_component_build = true\n"
"# is_debug = false\n"
- "# See \"gn args <dir_name> --list\" for available build "
+ "# See \"gn args <out_dir> --list\" for available build "
"arguments.\n";
#if defined(OS_WIN)
// Use Windows lineendings for this file since it will often open in
@@ -275,13 +275,13 @@ extern const char kArgs[] = "args";
extern const char kArgs_HelpShort[] =
"args: Display or configure arguments declared by the build.";
extern const char kArgs_Help[] =
- "gn args [arg name]\n"
+ "gn args <out_dir> [--list] [--short] [--args]\n"
"\n"
" See also \"gn help buildargs\" for a more high-level overview of how\n"
" build arguments work.\n"
"\n"
"Usage\n"
- " gn args <dir_name>\n"
+ " gn args <out_dir>\n"
" Open the arguments for the given build directory in an editor\n"
" (as specified by the EDITOR environment variable). If the given\n"
" build directory doesn't exist, it will be created and an empty\n"
@@ -294,7 +294,7 @@ extern const char kArgs_Help[] =
" \"args.gn\" in the build directory and then running\n"
" \"gn gen <build_dir>\".\n"
"\n"
- " gn args <dir_name> --list[=<exact_arg>] [--short]\n"
+ " gn args <out_dir> --list[=<exact_arg>] [--short]\n"
" Lists all build arguments available in the current configuration,\n"
" or, if an exact_arg is specified for the list flag, just that one\n"
" build argument.\n"
@@ -303,14 +303,14 @@ extern const char kArgs_Help[] =
" comment preceeding the declaration. If --short is specified,\n"
" only the names and values will be printed.\n"
"\n"
- " If the dir_name is specified, the build configuration will be\n"
+ " If the out_dir is specified, the build configuration will be\n"
" taken from that build directory. The reason this is needed is that\n"
" the definition of some arguments is dependent on the build\n"
" configuration, so setting some values might add, remove, or change\n"
" the default values for other arguments. Specifying your exact\n"
" configuration allows the proper arguments to be displayed.\n"
"\n"
- " Instead of specifying the dir_name, you can also use the\n"
+ " Instead of specifying the out_dir, you can also use the\n"
" command-line flag to specify the build configuration:\n"
" --args=<exact list of args to use>\n"
"\n"
« no previous file with comments | « no previous file | tools/gn/command_gen.cc » ('j') | tools/gn/command_refs.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698