Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(289)

Side by Side Diff: ppapi/ppapi.gyp

Issue 6981001: Make the Pepper proxy support in-process font rendering. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: '' Created 9 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « content/renderer/renderer_webkitclient_impl.cc ('k') | ppapi/ppapi_internal.gyp » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Copyright (c) 2010 The Chromium Authors. All rights reserved. 1 # Copyright (c) 2010 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 # This is the "public" ppapi.gyp file, which must have dependencies on the
6 # redistributable portions of PPAPI only. This prevents circular dependencies
7 # in the .gyp files (since ppapi_internal depends on parts of Chrome).
8
5 { 9 {
6 'variables': { 10 'variables': {
7 'chromium_code': 1, # Use higher warning level. 11 'chromium_code': 1, # Use higher warning level.
8 }, 12 },
9 'target_defaults': { 13 'target_defaults': {
10 'conditions': [ 14 'conditions': [
11 # Linux shared libraries should always be built -fPIC. 15 # Linux shared libraries should always be built -fPIC.
12 # 16 #
13 # TODO(ajwong): For internal pepper plugins, which are statically linked 17 # TODO(ajwong): For internal pepper plugins, which are statically linked
14 # into chrome, do we want to build w/o -fPIC? If so, how can we express 18 # into chrome, do we want to build w/o -fPIC? If so, how can we express
15 # that in the build system? 19 # that in the build system?
16 ['OS=="linux" or OS=="openbsd" or OS=="freebsd" or OS=="solaris"', { 20 ['OS=="linux" or OS=="openbsd" or OS=="freebsd" or OS=="solaris"', {
17 'cflags': ['-fPIC', '-fvisibility=hidden'], 21 'cflags': ['-fPIC', '-fvisibility=hidden'],
18 22
19 # This is needed to make the Linux shlib build happy. Without this, 23 # This is needed to make the Linux shlib build happy. Without this,
20 # -fvisibility=hidden gets stripped by the exclusion in common.gypi 24 # -fvisibility=hidden gets stripped by the exclusion in common.gypi
21 # that is triggered when a shared library build is specified. 25 # that is triggered when a shared library build is specified.
22 'cflags/': [['include', '^-fvisibility=hidden$']], 26 'cflags/': [['include', '^-fvisibility=hidden$']],
23 }], 27 }],
24 ], 28 ],
25 }, 29 },
26 'includes': [ 30 'includes': [
27 'ppapi_cpp.gypi', 31 'ppapi_cpp.gypi',
28 'ppapi_gl.gypi', 32 'ppapi_gl.gypi',
29 'ppapi_shared_proxy.gypi',
30 'ppapi_tests.gypi',
31 ], 33 ],
32 } 34 }
OLDNEW
« no previous file with comments | « content/renderer/renderer_webkitclient_impl.cc ('k') | ppapi/ppapi_internal.gyp » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698