From b5211dc74623948d3cbe5fed699a2eed2cc7df8b Mon Sep 17 00:00:00 2001 From: "joi@chromium.org" Date: Thu, 13 Sep 2012 13:10:10 +0000 Subject: [PATCH] include.gypi variables to specify API keys or use internal header for keys. BUG=145584 Review URL: https://codereview.chromium.org/10918196 git-svn-id: http://src.chromium.org/svn/trunk/src/build@156538 4ff67af0-8c30-449e-8e8b-ad334ec8d88c --- common.gypi | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/common.gypi b/common.gypi index f7453f866..b55b68e08 100644 --- a/common.gypi +++ b/common.gypi @@ -891,6 +891,24 @@ 'windows_sdk_default_path': '<(DEPTH)/third_party/platformsdk_win8/files', 'directx_sdk_default_path': '<(DEPTH)/third_party/directxsdk/files', + # Set these to bake API keys and OAuth client IDs/secrets into + # your build. If they are not baked in, you can instead set + # environment variables to provide the keys at runtime (see + # src/google_apis/google_api_keys.h for details). Features that + # require server-side APIs may fail to work if no keys are + # provided. + # + # Note that if you are building an official build or if you set + # use_official_google_api_keys to 1, these values will be ignored + # and the official keys will be used instead. + 'google_api_key%': '', + 'google_default_client_id%': '', + 'google_default_client_secret%': '', + + # Set this to 1 to use the Google-internal file containing + # official API keys for Google Chrome even in a developer build. + 'use_official_google_api_keys%': 0, + 'conditions': [ ['OS=="win" and "