diff options
| author | thakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-04 19:05:02 +0000 |
|---|---|---|
| committer | thakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-04 19:05:02 +0000 |
| commit | acad49654e2c232e6efb5ac7392298bbeb234a40 (patch) | |
| tree | fda5b512ea66c63f2788dee73706b0447d000c3c /google_apis | |
| parent | 93ea39da5423d641ecbc5687764f6b12972e302a (diff) | |
| download | chromium_src-acad49654e2c232e6efb5ac7392298bbeb234a40.zip chromium_src-acad49654e2c232e6efb5ac7392298bbeb234a40.tar.gz chromium_src-acad49654e2c232e6efb5ac7392298bbeb234a40.tar.bz2 | |
Use clang as default host compiler when cross-compiling
chrome/android still used system gcc as host compiler, and system gcc is
gcc 4.6 on Ubuntu Precise. This is too old.
Instead, use clang by default as host compiler (except when building for
AOSP, see http://crbug.com/377684 for that). This is controlled by a new
gyp variable host_clang, which only has an effect if clang=0. The existing
clang gyp variable means "use clang for everything"; if it's not set then
host_clang means "use clang for host compiles".
If your system gcc is 4.8+ and you don't want to use clang, you can set
host_clang=0 to use system gcc for host compiles instead.
In host_clang mode, our clang plugins currently aren't used (I figure if you
want plugins, you can just use clang=1). clang_warning_flags on the other
hand are used, to make sure the build stays warning-free.
BUG=360311
R=hans@chromium.org
Review URL: https://codereview.chromium.org/430383002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287386 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'google_apis')
0 files changed, 0 insertions, 0 deletions