Remove the 'gyp_config' concept from MB.

Remove the 'gyp_config' concept from MB.

Previously MB would try to ensure that the build directory
passed to it matched the expected gyp configuration for the bot
(i.e. that we would not pass "//out/Debug" as a path for a
release bot).

Making this work correctly was awkward for the Win x64 bots
(which use Release_x64 instead of Release), and it's not clear
that this check would ever actually catch a real problem.

So, this patch deletes all of the 'gyp_config' logic instead
and simplifies things.

TBR=scottmg@chromium.org
BUG=481692
Committed: https://crrev.com/fae80e312dba6818315f4f8f0c3a1d85f6f4f9fb
Cr-Commit-Position: refs/heads/master@{#349043}

[Dirk Pranke, 2015-09-15 22:24:51]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2015-09-15 22:25:20]

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

[Dirk Pranke, 2015-09-15 22:28:02]

This should fix the build failures on the Win x64 Builder on chromium.perf that
started when I enabled MB on the perf bots.

http://build.chromium.org/p/chromium.perf/builders/Win%20x64%20Builder/builds...

[scottmg, 2015-09-15 22:32:26]

lgtm

https://codereview.chromium.org/1348463002/diff/1/tools/mb/docs/user_guide.md
File tools/mb/docs/user_guide.md (right):

https://codereview.chromium.org/1348463002/diff/1/tools/mb/docs/user_guide.md...
tools/mb/docs/user_guide.md:185: mixins; gyp_defines and gn_args values are
concatenated, and the type value
values override?

[Dirk Pranke, 2015-09-15 22:37:07]

https://codereview.chromium.org/1348463002/diff/1/tools/mb/docs/user_guide.md
File tools/mb/docs/user_guide.md (right):

https://codereview.chromium.org/1348463002/diff/1/tools/mb/docs/user_guide.md...
tools/mb/docs/user_guide.md:185: mixins; gyp_defines and gn_args values are
concatenated, and the type value
On 2015/09/15 22:32:26, scottmg wrote:
> values override?

will fix.

[Dirk Pranke, 2015-09-15 22:37:10]

The CQ bit was checked by dpranke@chromium.org

[Dirk Pranke, 2015-09-15 22:37:10]

The patchset sent to the CQ was uploaded after l-g-t-m from scottmg@chromium.org
Link to the patchset: https://codereview.chromium.org/1348463002/#ps20001
(title: "s/type value/type values")

[commit-bot: I haz the power, 2015-09-15 22:37:24]

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

[commit-bot: I haz the power, 2015-09-16 00:16:27]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-09-16 00:17:42]

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

[Dirk Pranke, 2015-09-16 00:23:44]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/1349463003/ by dpranke@chromium.org.

The reason for reverting is: Looks like the output_dir part of this is wrong:
...

http://build.chromium.org/p/chromium.perf/builders/Win%20x64%20Builder/builds....

[commit-bot: I haz the power, 2015-09-23 12:51:36]

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