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

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

The output directory is the same as the build directory, so let's be
consistent to not confuse new users.

BUG=441955
TEST=gn help args, gn help gen, gn help ls, gn help refs
R=scottmg@chromium.org

Committed: https://crrev.com/f575e01d05e216389f358356adcc8c46f23f36d5
Cr-Commit-Position: refs/heads/master@{#314324}

[tfarina, 2015-02-02 00:55:20]

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_args.cc
File tools/gn/command_args.cc (right):

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_args.cc#new...
tools/gn/command_args.cc:290: "          enable_doom_melon=false\n"
Do we bother changing this? It seems fine or should we change to 'is_debug' for
example?

[mdempsky, 2015-02-02 01:05:18]

mdempsky@chromium.org changed reviewers:
+ mdempsky@chromium.org

[mdempsky, 2015-02-02 01:05:18]

lgtm, fwiw

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_args.cc
File tools/gn/command_args.cc (right):

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_args.cc#new...
tools/gn/command_args.cc:290: "          enable_doom_melon=false\n"
On 2015/02/02 00:55:20, tfarina wrote:
> Do we bother changing this? It seems fine or should we change to 'is_debug'
for
> example?

FWIW, I think it makes sense to be consistent with the examples.  Also, the
previous issue of "os" isn't actually an assignable argument (IIRC) still seems
relevant here.

[scottmg, 2015-02-02 02:18:43]

lgtm

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_refs.cc
File tools/gn/command_refs.cc (right):

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_refs.cc#new...
tools/gn/command_refs.cc:285: "Usage: \"gn refs <build_dir>
(<label_pattern>|<file>)\"")
another one here

[tfarina, 2015-02-03 02:10:58]

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_refs.cc
File tools/gn/command_refs.cc (right):

https://codereview.chromium.org/895433002/diff/1/tools/gn/command_refs.cc#new...
tools/gn/command_refs.cc:285: "Usage: \"gn refs <build_dir>
(<label_pattern>|<file>)\"")
On 2015/02/02 02:18:43, scottmg wrote:
> another one here

Done.

[tfarina, 2015-02-03 02:11:02]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2015-02-03 02:11:54]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/895433002/20001

[commit-bot: I haz the power, 2015-02-03 04:12:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-03 04:12:57]

Try jobs failed on following builders:
  win8_chromium_rel on tryserver.chromium.win (None)

[tfarina, 2015-02-03 13:34:35]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2015-02-03 13:34:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/895433002/20001

[commit-bot: I haz the power, 2015-02-03 13:35:32]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-03 13:36:38]

Patchset 2 (id:??) landed as
https://crrev.com/f575e01d05e216389f358356adcc8c46f23f36d5
Cr-Commit-Position: refs/heads/master@{#314324}