Move instrumented-libraries-related settings out of common.gypi.

Move instrumented-libraries-related settings out of common.gypi.

Instead, apply them as direct_dependent_settings to dependents of the
instrumented_libraries target. This is functionally equivalent, but reduces code
duplication, improves locality and also allows us to disable the use of
instrumented libraries on a target-by-target basis.

BUG=313751
TBR=glider@chromium.org
TEST=MSan
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=264281

[earthdok, 2014-04-16 18:19:35]

PTAL

When I switch between this and ToT, nothing is rebuilt, so looks like zero
functionality change.

[earthdok, 2014-04-16 19:19:50]

committing with NOTRY

[earthdok, 2014-04-16 19:19:54]

The CQ bit was checked by earthdok@chromium.org

[commit-bot: I haz the power, 2014-04-16 19:22:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/earthdok@chromium.org/240413004/1

[commit-bot: I haz the power, 2014-04-16 19:23:28]

Change committed as 264281

[Nico, 2014-04-16 19:30:06]

On 2014/04/16 18:19:35, earthdok wrote:
> PTAL
> 
> When I switch between this and ToT, nothing is rebuilt, so looks like zero
> functionality change.

(I sometimes create ninja files with and without my change into different output
directories using -Goutput_dir, and then compare the generated ninja files for
checks like this.)

[earthdok, 2014-04-16 19:34:55]

On 2014/04/16 19:30:06, Nico wrote:
> (I sometimes create ninja files with and without my change into different
output
> directories using -Goutput_dir, and then compare the generated ninja files for
> checks like this.)

Thanks for the tip!