New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 624533 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

gn args --list without build dir doesn't work

Project Member Reported by scottmg@chromium.org, Jun 29 2016

Issue description

From gn help args:

"""
...
Examples
...
  gn args --list --args="os=\"android\" enable_doom_melon=true"
    Prints all arguments with the default values for a build with the
    given arguments set (which may affect the values of other
    arguments).
"""

but 

[994b8ad...]d:\src\cr3\src>gn args --list --args="os=\"android\" enable_doom_melon=true"
ERROR Exactly one build dir needed.
Usage: "gn args <out_dir>"
Or see "gn help args" for more variants.


It might be nice if this worked. Specifying a build dir always seems a bit tiring on the command line.

But otherwise, I guess we should just delete the --args helptext/example.
 

Comment 1 by brettw@chromium.org, Aug 17 2016

Status: WontFix (was: Untriaged)
This is not possible because the list of args will vary with build type. GN has to execute the files in some context to know what the args are, and the build directory specifies this context.

It used to support a default directory but this was confusing and I removed it.
OK, we should delete the no-build-dir example then.

Sign in to add a comment