In clang builds, we use the same compiler binary for 32-bit and 64-bit
builds, so we need to tell that binary if it should produce 32-bit or
64-bit object files.
The //build/config/compiler:compiler config takes care of adding -m32
and -m64 flags, but the mini_installer target removed that config,
removing these flags (and other important compiler flags such as
-fmsc-version).
It looks like removing this config isn't really necessary -- the only
compiler flag that mini_installer wants to change is /GS-, to disable
buffer security checks. I first thought I'd move /GS into its own
config so that mini_installer can remove it, but it turns out /GS is
on by default. So don't pass /GS in :compiler, and do pass /GS- in
mini_installer.
No target should remove //build/config/compiler:compiler from its configs.
BUG=498033
Review-Url: https://codereview.chromium.org/1957523005
Cr-Original-Commit-Position: refs/heads/master@{#392175}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 7170da48a964aa08a16fbf03ce17dbd78b596500
f9105f04b0