gn: Use the term 'out_dir' consistently when referring to the output directory.

tools/gn/command_args.cc

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include <stdio.h>
 #include <stdlib.h>
 
 #include <map>
 
 #include "base/command_line.h"
@@ skipping 227 matching lines @@
     // Windows they can come out as forward slashes here, and that confuses some
     // of the commands.
     base::FilePath arg_file =
         setup.build_settings().GetFullPath(setup.GetBuildArgFile())
         .NormalizePathSeparators();
     if (!base::PathExists(arg_file)) {
       std::string argfile_default_contents =
           "# 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
       // Notepad which can't handle Unix ones.
       ReplaceSubstringsAfterOffset(&argfile_default_contents, 0, "\n", "\r\n");
 #endif
       base::CreateDirectory(arg_file.DirName());
       base::WriteFile(arg_file, argfile_default_contents.c_str(),
                       static_cast<int>(argfile_default_contents.size()));
     }
 
     ScopedTrace editor_trace(TraceItem::TRACE_SETUP, "Waiting for editor");
     if (!RunEditor(arg_file))
       return 1;
   }
 
   // Now do a normal "gen" command.
   OutputString("Generating files...\n");
   std::vector<std::string> gen_commands;
   gen_commands.push_back(build_dir);
   return RunGen(gen_commands);
 }
 
 }  // namespace
 
 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"
     "      args file will be opened in the editor. You would type something\n"
     "      like this into that file:\n"
     "          enable_doom_melon=false\n"
     "          os=\"android\"\n"
     "\n"
     "      Note: you can edit the build args manually by editing the file\n"
     "      \"args.gn\" in the build directory and then running\n"
-    "      \"gn gen <build_dir>\".\n"
+    "      \"gn gen <out_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"
     "\n"
     "      The output will list the declaration location, default value, and\n"
     "      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"
     "Examples\n"
     "  gn args out/Debug\n"
     "    Opens an editor with the args for out/Debug.\n"
     "\n"
     "  gn args out/Debug --list --short\n"
     "    Prints all arguments with their default values for the out/Debug\n"
     "    build.\n"
     "\n"
     "  gn args out/Debug --list=cpu_arch\n"
     "    Prints information about the \"cpu_arch\" argument for the out/Debug\n"
     "    build.\n"
     "\n"
     "  gn args --list --args=\"os=\\\"android\\\" enable_doom_melon=true\"\n"
     "    Prints all arguments with the default values for a build with the\n"
     "    given arguments set (which may affect the values of other\n"
     "    arguments).\n";
 
 int RunArgs(const std::vector<std::string>& args) {
   if (args.size() != 1) {
     Err(Location(), "Exactly one build dir needed.",
-        "Usage: \"gn args <build_dir>\"\n"
+        "Usage: \"gn args <out_dir>\"\n"
         "Or see \"gn help args\" for more variants.").PrintToStdout();
     return 1;
   }
 
   if (base::CommandLine::ForCurrentProcess()->HasSwitch(kSwitchList))
     return ListArgs(args[0]);
   return EditArgsFile(args[0]);
 }
 
 }  // namespace commands