Make the Pepper proxy support in-process font rendering.

This implements a WebKit thread in the PPAPI plugin process so we can do the
font calls without IPC. The existing font support was refactored into
a virtual class (to prevent PPAPI from depending on WebKit and creating a
circular GYP dependency).

This moves the renderer sandbox support into content/common so that it can
be used by the PPAPI process.
Review URL: http://codereview.chromium.org/6981001

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84856 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 30 insertions, 0 deletions

diff --git a/ppapi/ppapi_internal.gyp b/ppapi/ppapi_internal.gyp
new file mode 100644
index 0000000..520c3cc
--- /dev/null
+++ b/ppapi/ppapi_internal.gyp
@@ -0,0 +1,30 @@
+# Copyright (c) 2010 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.
+
+{
+  'variables': {
+    'chromium_code': 1,  # Use higher warning level.
+  },
+  'target_defaults': {
+    'conditions': [
+      # Linux shared libraries should always be built -fPIC.
+      #
+      # TODO(ajwong): For internal pepper plugins, which are statically linked
+      # into chrome, do we want to build w/o -fPIC?  If so, how can we express
+      # that in the build system?
+      ['OS=="linux" or OS=="openbsd" or OS=="freebsd" or OS=="solaris"', {
+        'cflags': ['-fPIC', '-fvisibility=hidden'],
+
+        # This is needed to make the Linux shlib build happy. Without this,
+        # -fvisibility=hidden gets stripped by the exclusion in common.gypi
+        # that is triggered when a shared library build is specified.
+        'cflags/': [['include', '^-fvisibility=hidden$']],
+      }],
+    ],
+  },
+  'includes': [
+    'ppapi_shared_proxy.gypi',
+    'ppapi_tests.gypi',
+  ],
+}