summaryrefslogtreecommitdiffstats
path: root/chrome_frame/bho_loader.h
diff options
context:
space:
mode:
authorpeter@chromium.org <peter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-20 16:44:21 +0000
committerpeter@chromium.org <peter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-20 16:44:21 +0000
commitfd65df7434e0cc14bc88a4bf192a65619598f864 (patch)
treee84ea9dbd638d61ebea146d05ec5da3f1061a9b9 /chrome_frame/bho_loader.h
parent0254ebe9642646286150040abb610b94f005d66a (diff)
downloadchromium_src-fd65df7434e0cc14bc88a4bf192a65619598f864.zip
chromium_src-fd65df7434e0cc14bc88a4bf192a65619598f864.tar.gz
chromium_src-fd65df7434e0cc14bc88a4bf192a65619598f864.tar.bz2
Don't rely on the Android toolchain being exported in the PATH for the {CC,CXX,LINK,AR}_target defines.
The make build has start using these environment variables since gyp revision 1470[1]. This works in the Chromium repository as the Android toolchain is being exported in the PATH, which is something WebKit doesn't do, and we shouldn't be relying on in general. Instead, use the paths to the toolchain and prefix them with Android's goma wrapper, which yields the same effect. [1] https://code.google.com/p/gyp/source/detail?r=1470 BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10827419 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152340 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/bho_loader.h')
0 files changed, 0 insertions, 0 deletions