[Mac/GN] dSYM output always goes in root_out_dir, so specify it in linker outputs.

[Mac/GN] dSYM output always goes in root_out_dir, so specify it in linker outputs.

This was causing overbuild for targets that override the output directory,
since the linker_driver.py is configured to place dSYMs in root_out_dir, but
the linker output was listed in the target_out_dir.

BUG=330301, 431177
R=brettw@chromium.org

Committed: https://crrev.com/0dda1538d9a8e10e8ad5288b3c2a71cd2437b643
Cr-Commit-Position: refs/heads/master@{#398739}

[brettw, 2016-06-08 22:19:49]

lgtm

[Robert Sesek, 2016-06-08 22:52:14]

The CQ bit was checked by rsesek@chromium.org

[commit-bot: I haz the power, 2016-06-08 22:52:35]

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

[commit-bot: I haz the power, 2016-06-08 23:59:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-09 00:01:01]

Description was changed from

==========
[Mac/GN] dSYM output always goes in root_out_dir, so specify it in linker
outputs.

This was causing overbuild for targets that override the output directory,
since the linker_driver.py is configured to place dSYMs in root_out_dir, but
the linker output was listed in the target_out_dir.

BUG=330301,431177
R=brettw@chromium.org
==========

to

==========
[Mac/GN] dSYM output always goes in root_out_dir, so specify it in linker
outputs.

This was causing overbuild for targets that override the output directory,
since the linker_driver.py is configured to place dSYMs in root_out_dir, but
the linker output was listed in the target_out_dir.

BUG=330301,431177
R=brettw@chromium.org

Committed: https://crrev.com/0dda1538d9a8e10e8ad5288b3c2a71cd2437b643
Cr-Commit-Position: refs/heads/master@{#398739}
==========

[commit-bot: I haz the power, 2016-06-09 00:01:02]

Patchset 1 (id:??) landed as
https://crrev.com/0dda1538d9a8e10e8ad5288b3c2a71cd2437b643
Cr-Commit-Position: refs/heads/master@{#398739}