Chromium Code Reviews| Index: content/content_components_tracing.gyp |
| diff --git a/content/content_components_tracing.gyp b/content/content_components_tracing.gyp |
| new file mode 100644 |
| index 0000000000000000000000000000000000000000..2de31c1579046e47c3414838319fc3d56a9b6027 |
| --- /dev/null |
| +++ b/content/content_components_tracing.gyp |
| @@ -0,0 +1,57 @@ |
| +# Copyright (c) 2012 The Chromium Authors. All rights reserved. |
| +# |
| +# Use of this source code is governed by a BSD-style license that can be |
| +# found in the LICENSE file. |
| + |
|
bbudge
2012/12/05 02:22:28
The usual pattern when supporting a NaCl (untruste
|
| +{ |
| + 'includes': [ |
| + '../build/common_untrusted.gypi', |
|
bbudge
2012/12/05 02:22:28
Specifically it worries me to include this in the
|
| + ], |
| + 'conditions': [ |
| + ['disable_nacl==0 and disable_nacl_untrusted==0', { |
| + 'targets': [ |
| + { |
| + 'target_name': 'tracing_untrusted', |
| + 'type': 'none', |
| + 'defines!': ['CONTENT_IMPLEMENTATION'], |
| + 'dependencies': [ |
| + '../base/base_untrusted.gyp:base_untrusted', |
| + '../native_client/tools.gyp:prep_toolchain', |
| + '../ipc/ipc.gyp:ipc', |
| + ], |
| + 'include_dirs': [ |
| + '..', |
| + ], |
| + 'variables': { |
| + 'nacl_untrusted_build': 1, |
| + 'nlib_target': 'libtracing_untrusted.a', |
| + 'build_glibc': 0, |
| + 'build_newlib': 1, |
| + }, |
| + 'sources': [ |
| + 'components/tracing/tracing_messages.cc', |
| + 'components/tracing/tracing_messages.h', |
| + ], |
| + }, |
| + ], |
| + }], |
| + ], |
| + 'targets' : [ |
| + { |
| + 'target_name': 'tracing', |
| + 'type': 'static_library', |
| + 'defines!': ['CONTENT_IMPLEMENTATION'], |
| + 'dependencies': [ |
| + '../base/base.gyp:base', |
| + '../ipc/ipc.gyp:ipc', |
| + ], |
| + 'include_dirs': [ |
| + '..', |
| + ], |
| + 'sources': [ |
| + 'components/tracing/tracing_messages.cc', |
| + 'components/tracing/tracing_messages.h', |
| + ], |
| + }, |
| + ], |
| +} |