1 # Copyright 2013 The Chromium Authors. All rights reserved.
2 # Use of this source code is governed by a BSD-style license that can be
3 # found in the LICENSE file.
5 # This is the set of recommended gyp variable settings for Chrome for Android development.
7 # These can be used by copying this file to $CHROME_SRC/chrome/supplement.gypi.
9 # Even better, create chrome/supplement.gypi containing the following:
11 # 'includes': [ '../build/android/developer_recommended_flags.gypi' ]
13 # and you'll get new settings automatically.
14 # When using this method, you can override individual settings by setting them unconditionally (with
15 # no %) in chrome/supplement.gypi.
16 # I.e. to disable optimize_jni_generation but use everything else:
19 # 'optimize_jni_generation': 0,
21 # 'includes': [ '../build/android/developer_recommended_flags.gypi' ]
27 # Set component to 'shared_library' to enable the component build. This builds native code as
28 # many small shared libraries instead of one monolithic library. This slightly reduces the time
29 # required for incremental builds.
30 'component%': 'shared_library',
32 'component%': '<(component)',
34 # When set to 1, only write jni generated files if they've changed. This can prevent unnecessary
35 # compiling/linking of native libraries when editing java files.
36 'optimize_jni_generation%': 1,
38 # When gyp_managed_install is set to 1, building an APK will install that APK on the connected
39 # device(/emulator). To install on multiple devices (or onto a new device), build the APK once
40 # with each device attached. This greatly reduces the time required for incremental builds.
42 # This comes with some caveats:
43 # Only works with a single device connected (it will print a warning if
44 # zero or multiple devices are attached).
45 # Some actions are always run (i.e. ninja will never say "no work to do").
46 'gyp_managed_install%': 1,
48 # With gyp_managed_install, we do not necessarily need a standalone APK.
49 # When create_standalone_apk is set to 1, we will build a standalone APK
50 # anyway. For even faster builds, you can set create_standalone_apk to 0.
51 'create_standalone_apk%': 1,
53 # Set clang to 1 to use the clang compiler. Clang has much (much, much) better warning/error
55 # TODO(cjhopman): Enable this when http://crbug.com/156420 is addressed. Until then, users can
56 # set clang to 1, but Android stack traces will sometimes be incomplete.
59 # Set fastbuild to 1 to build with less debugging information. This can greatly decrease linking
60 # time. The downside is that stack traces will be missing useful information (like line