OLD | NEW |
1 # Copyright (c) 2009 The Chromium Authors. All rights reserved. | 1 # Copyright (c) 2009 The Chromium Authors. All rights reserved. |
2 # Use of this source code is governed by a BSD-style license that can be | 2 # Use of this source code is governed by a BSD-style license that can be |
3 # found in the LICENSE file. | 3 # found in the LICENSE file. |
4 | 4 |
5 # IMPORTANT: | 5 # IMPORTANT: |
6 # Please don't directly include this file if you are building via gyp_chromium, | 6 # Please don't directly include this file if you are building via gyp_chromium, |
7 # since gyp_chromium is automatically forcing its inclusion. | 7 # since gyp_chromium is automatically forcing its inclusion. |
8 { | 8 { |
9 'variables': { | 9 'variables': { |
10 # .gyp files should set chromium_code to 1 if they build Chromium-specific | 10 # .gyp files should set chromium_code to 1 if they build Chromium-specific |
(...skipping 31 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
42 # situations. I.e. for Chrome bot. | 42 # situations. I.e. for Chrome bot. |
43 'linux_chromium_breakpad%': 0, | 43 'linux_chromium_breakpad%': 0, |
44 | 44 |
45 # By default, Linux does not use views. To turn on views in Linux, | 45 # By default, Linux does not use views. To turn on views in Linux, |
46 # set the variable GYP_DEFINES to "toolkit_views=1", or modify | 46 # set the variable GYP_DEFINES to "toolkit_views=1", or modify |
47 # ~/.gyp/include.gypi . | 47 # ~/.gyp/include.gypi . |
48 'toolkit_views%': 0, | 48 'toolkit_views%': 0, |
49 | 49 |
50 # Defaults to a desktop build, overridden via command line/env. | 50 # Defaults to a desktop build, overridden via command line/env. |
51 'chromeos%': 0, | 51 'chromeos%': 0, |
| 52 |
| 53 # This variable tells WebCore.gyp and JavaScriptCore.gyp whether they are |
| 54 # are built under a chromium full build (1) or a webkit.org chromium |
| 55 # build (0). |
| 56 'inside_chromium_build%': 1, |
52 }, | 57 }, |
53 | 58 |
54 # Define branding and buildtype on the basis of their settings within the | 59 # Define branding and buildtype on the basis of their settings within the |
55 # variables sub-dict above, unless overridden. | 60 # variables sub-dict above, unless overridden. |
56 'branding%': '<(branding)', | 61 'branding%': '<(branding)', |
57 'buildtype%': '<(buildtype)', | 62 'buildtype%': '<(buildtype)', |
58 'target_arch%': '<(target_arch)', | 63 'target_arch%': '<(target_arch)', |
59 'toolkit_views%': '<(toolkit_views)', | 64 'toolkit_views%': '<(toolkit_views)', |
60 'chromeos%': '<(chromeos)', | 65 'chromeos%': '<(chromeos)', |
| 66 'inside_chromium_build%': '<(inside_chromium_build)', |
61 | 67 |
62 # Override chromium_mac_pch and set it to 0 to suppress the use of | 68 # Override chromium_mac_pch and set it to 0 to suppress the use of |
63 # precompiled headers on the Mac. Prefix header injection may still be | 69 # precompiled headers on the Mac. Prefix header injection may still be |
64 # used, but prefix headers will not be precompiled. This is useful when | 70 # used, but prefix headers will not be precompiled. This is useful when |
65 # using distcc to distribute a build to compile slaves that don't | 71 # using distcc to distribute a build to compile slaves that don't |
66 # share the same compiler executable as the system driving the compilation, | 72 # share the same compiler executable as the system driving the compilation, |
67 # because precompiled headers rely on pointers into a specific compiler | 73 # because precompiled headers rely on pointers into a specific compiler |
68 # executable's image. Setting this to 0 is needed to use an experimental | 74 # executable's image. Setting this to 0 is needed to use an experimental |
69 # Linux-Mac cross compiler distcc farm. | 75 # Linux-Mac cross compiler distcc farm. |
70 'chromium_mac_pch%': 1, | 76 'chromium_mac_pch%': 1, |
(...skipping 781 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
852 # settings in target dicts. SYMROOT is a special case, because many other | 858 # settings in target dicts. SYMROOT is a special case, because many other |
853 # Xcode variables depend on it, including variables such as | 859 # Xcode variables depend on it, including variables such as |
854 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something | 860 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something |
855 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the | 861 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the |
856 # files to appear (when present) in the UI as actual files and not red | 862 # files to appear (when present) in the UI as actual files and not red |
857 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR, | 863 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR, |
858 # and therefore SYMROOT, needs to be set at the project level. | 864 # and therefore SYMROOT, needs to be set at the project level. |
859 'SYMROOT': '<(DEPTH)/xcodebuild', | 865 'SYMROOT': '<(DEPTH)/xcodebuild', |
860 }, | 866 }, |
861 } | 867 } |
OLD | NEW |