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

Issue 837876 link

Starred by 2 users
Status: Fixed
Owner:
dpranke@chromium.org
Closed: Jun 2018
Cc:
liaoyuke@chromium.org
martiniss@chromium.org
█ brettw@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

No way to figure out which target generates an executable in GN

Project Member Reported by dpranke@chromium.org, Apr 28 2018 
It would be useful for there to be a way to ask GN "which target generates this executable" but that doesn't currently seem to be possible.

Specifically, `gn refs out/Default //out/Default/gn` should probably return something, and it doesn't.

It looks like refs doesn't look at the actual output files for a target, even though the docs suggest that it should.
Project Member

Comment 1 by bugdroid1@chromium.org, May 1 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3d36fd0d000ced51aa0a2848b1df0b2cd36cc4c5

commit 3d36fd0d000ced51aa0a2848b1df0b2cd36cc4c5
Author: Dirk Pranke <dpranke@chromium.org>
Date: Tue May 01 19:17:34 2018

Make `gn refs out/foo //out/foo/gn` work.

It would be good if we could use `gn refs` to tell us which
target generated a given executable. The docs suggested that
refs should do this, but it doesn't appear to do so.

Bug:  837876 
Change-Id: I45f45bb3346ed21ede83fbacdea2207f1322ad69
Reviewed-on: https://chromium-review.googlesource.com/1033506
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555134}
[modify] https://crrev.com/3d36fd0d000ced51aa0a2848b1df0b2cd36cc4c5/tools/gn/command_refs.cc

Comment 2 by dpranke@chromium.org, Jun 16 2018

Status: Fixed (was: Started)
I think this is fixed now ...
►

Sign in to add a comment